commit

Conventional Commits 1.0 generator. Stages relevant files, infers type(scope): description, never uses --no-verify.

不碰外部（只输出文字）无严重或高危命中hashgraph-online/awesome-codex-plugins

它会碰到什么

扫了多少1 个文本文件，2 KB

它会碰到什么不碰外部（只输出文字）

命中总数0 处

命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实，不是结论。命中多不等于有毒（安全工具、规则库、示例脚本本来就会包含危险写法），命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系，需要你自己看。

技能内容

Commit — Conventional Commits Generator

When to Trigger

User wants to commit, save, or check in changes
User asks to commit after completing a task
Code changes are ready and user signals completion

Process

Gather context — run in parallel:

git status — see what changed
git diff HEAD — see the actual diff
git log --oneline -5 — match existing commit style

Determine type:

| Type | When |

|------|------|

| feat | New feature or capability |

| fix | Bug fix |

| refactor | Code change, no behavior change |

| docs | Documentation only |

| test | Adding or correcting tests |

| build | Build system or dependencies |

| chore | Maintenance task |

| ci | CI/CD configuration |

| style | Formatting, whitespace |

| perf | Performance improvement |

Generate message: type(scope): description

Lowercase type, optional scope
Imperative mood, no period, under 72 chars
Breaking changes: append ! before :
Body only when diff needs extra context (max 3 bullet points)

Stage and commit:

git add <specific files> — prefer explicit files over git add -A
git commit -m "type(scope): description"
Execute automatically — no confirmation needed

Anti-Rationalization

| Excuse | Rebuttal | What to do instead |

|--------|----------|-------------------|

| "I'll just use a generic message" | Generic messages make git history useless. | Spend 5 seconds analyzing the diff — the type and scope are obvious from the changes. |

| "The user didn't specify a format" | Conventional Commits is the project standard — guard will block non-CC messages anyway. | Always generate CC format. |

| "I'll commit everything together" | Unrelated changes in one commit make bisect and revert impossible. | If changes span multiple concerns, suggest splitting first. |