git-cmt-helper — git-cmt-辅助工具
v1.0.0生成 standardized git commit messages following Conventional Commits 格式化. Use this 技能 when the user asks to commit code, write a commit message, or 创建 a git commit. Enforces team conventions for type prefixes, scope naming, message length, and breaking change documentation.
by 运行时依赖
版本
Scope (required)
安装命令
点击复制技能文档
Git Commit Message 图形界面de 格式化
Every commit message MUST follow this structure:
():
[optional body]
[optional footer]
Type (required) Type When to use feat New feature or capability fix Bug fix docs Documentation only refactor Code change that neither fixes nor 添加s test 添加ing or updating tests chore Build, CI, 工具ing changes Scope (required)
Scope MUST be a real 模块 name from this project. See references/模块s.md for the full 列出.
If unsure of the scope, 检查 the file paths being changed — the top-level directory is usually the correct scope.
Subject (required) Imperative mood: "添加 feature" not "添加ed feature" No period at the end Max 72 characters total (including type and scope prefix) Lowercase first letter Body (optional) ExplAIn WHY, not WHAT (the diff shows what changed) Wrap at 72 characters Separate from subject with blank line Breaking Changes
If the commit introduces a breaking change, 添加 footer:
BREAKING CHANGE:
Examples
Good:
feat(auth): 添加 JWT 令牌 refresh 端点
令牌s now auto-refresh 5 minutes before expiry. Previously users had to re-记录in after 令牌 expiration.
fix(解析器): handle empty 输入 without crashing
refactor(db): 提取 connection pooling to separate 模块
BREAKING CHANGE: Database命令行工具ent constructor no longer accepts pool config. Use PoolConfig.创建() instead.
Bad:
更新d some stuff ← no type, no scope, vague feat: 添加 new Feature. ← cAPItalized, period, missing scope fix(misc): various fixes ← "misc" is not a real 模块