Agent Skills
› lthoangg/OpenAgentd
› oad/commit
oad/commit
GitHub指导生成符合规范的高质量 Git Commit，涵盖暂存、分析变更影响、同步文档及生成结构化提交信息。
Trigger Scenarios
用户请求创建 Git Commit
需要规范化提交消息时
Install
npx skills add lthoangg/OpenAgentd --skill oad/commit -g -y
SKILL.md
Frontmatter
{
"name": "oad\/commit",
"description": "OpenAgentd workflow for well-formatted, detailed conventional commits."
}
Git Commit Execution Workflow
- Stage: Run
git status --porcelain. If no files are staged, executegit add .. - Analyze: Run
git diff --cachedto evaluate the technical scope and architectural impact (e.g., DDD shifts or C4 updates). - Sync Docs: Load
oad/docsto sync any documentation affected by the staged changes. - Generate Message:
- Format:
<type>: <subject> - Subject: Auto-generate a concise imperative subject from the staged changes.
- Body: Leave a blank line, then detail Motivation, Technical Changes (bulleted deep-dive), and Impact.
- Format:
- Commit: Execute
git commit -m "<message>"and output the commit hash and a brief summary.
Note: Multiple commits are preferred for large changes. If the scope is too broad, break it down into smaller, focused commits following the same workflow (do not force to have multiple commits if the change is small and cohesive).
Sizing: target ~100 changed lines per commit (a single logical, self-contained change); ~300 is acceptable for one cohesive change; ~1000+ should be split. Keep refactors and behavior changes in separate commits — mixing "renamed X" with "fixed Y" makes both harder to review and revert.
Commit Conventions
| Category | Type |
|---|---|
| Features | feat |
| Fixes | fix |
| Refactor | refactor |
| Maintenance | chore/docs |
| Style | style |
Version History
- b4ec0d3 Current 2026-07-24 16:51
