Agent Skills
› lthoangg/OpenAgentd
› oad/commit
oad/commit
GitHub提供符合规范的 Git Commit 工作流，自动暂存、分析变更并生成结构化提交信息。支持按类型（feat/fix等）和大小拆分提交，确保日志清晰可追溯。
触发场景
需要提交代码更改时
生成符合 Conventional Commits 规范的提交消息时
安装
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 |
版本历史
- b4ec0d3 当前 2026-07-24 16:51
