commit-helper
Skill1 starsChanged 4 months agoMITView on GitHub
在提交前按当前仓库约定分析变更，优先按领域拆分为多个原子 commit，并生成可直接使用的 git commit message。
10 other projects use a version of this.
Adopted by
Most recently taken up by
- aidankaokao/claude-skillstheir own version, first seen Oct 9, 2026
- chmouel/lazyworktreetheir own version, first seen Oct 8, 2026
- cockroachdb/cockroachtheir own version, first seen Oct 8, 2026
- toilanguyen2910/claude-code-starter-packtheir own version, first seen Oct 3, 2026
- 17-sss/agent-skillstheir own version, first seen Sep 22, 2026
- almax000/claude-skillstheir own version, first seen Apr 19, 2026
Used with
Projects with it also use code-reviewer.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillcode-reviewer
Also in 4 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- cockroachdb/cockroach★ 33ksame name
- chmouel/lazyworktree★ 315same name
- nimbalyst/skills★ 28same name
- nodnarbnitram/claude-code-extensions★ 16same name
- peopleforrester/claude-dotfiles★ 3same name
- 17-sss/agent-skills★ 2same name
- almax000/claude-skills★ 1same name
- AntonioZS/claude-skills-mcp★ 1same name
- toilanguyen2910/claude-code-starter-pack★ 1same name
- aidankaokao/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Files
请基于当前仓库的变更，为即将执行的提交生成符合仓库约定的 commit message。
提交规范
- 优先使用约定式提交：
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]type使用：feat、fix、refactor、docs、test、chore- 提交说明使用中文描述变更目的，专业术语保留英文
- 保持原子化提交：一次 commit 只包含一个逻辑变更
你的任务
- 先查看当前变更，优先读取 staged diff；如果没有 staged 变更，再看工作区变更
- 先做“是否需要拆分提交”的判断，而不是默认把所有变更合并成 1 次提交
- 按业务领域、子系统边界、变更目的评估是否属于不同原子变更；只要跨领域、跨模块且可以独立提交，就应拆分
- 常见应拆分场景包括但不限于：服务端与客户端、算法与接口层、测试与生产代码、重构与功能修复、文档与代码、不同目录下互不依赖的业务变更
- 如果变更其实服务于同一个目的，即使涉及多个文件，也应保持为 1 次提交，不要机械按文件数拆分
- 对每个建议提交分别判断最合适的
type，必要时补充简短scope - 直接产出可用于提交的 commit message；如果需要拆分，按提交顺序给出多条 message，并明确每条对应的文件/变更范围
- 只有在用户已经提供 commit message 草稿时，才做规范性修正
- 提交后记得先 pull，然后 push
输出约束
- 以可直接提交的 commit message 为核心输出
- 不要直接执行
git commit - 不要输出与提交规范无关的长篇说明
subject保持简洁，聚焦“为什么改”而不是流水账式“改了什么”- 如果无法判断
scope，可省略 - 如果建议拆分提交，输出格式优先为：
Commit 1/Commit 2...，每项包含“建议纳入的文件或领域”与对应 commit message - 如果判断不需要拆分，也要明确说明“建议单次提交”的原因
用户补充背景：
$ARGUMENTS
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.