commit
Create a git commit with a good message. Use when the user says "commit", "save changes", "commit this", or asks to create a commit after making code changes.
来源信息
- 仓库
- TuYv/ccpm
- 最近来源活动
- 2026年9月26日 14:16
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 1
- 分支
- 2
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
3 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- commit
- description
- Create a git commit with a good message. Use when the user says "commit", "save changes", "commit this", or asks to create a commit after making code changes.
- allowed-tools
- Bash, Read, Grep, Glob
# Git Commit
Review all staged changes and create a well-crafted commit message.
## Steps
1. Run `git status` to see staged and unstaged changes
2. Run `git diff --cached` to review staged changes in detail
3. If nothing is staged, run `git diff` and suggest what to stage based on the changes
4. Run `git log --oneline -5` to see recent commit message style in the repo
5. Draft a concise commit message following conventional commits format:
- `feat:` — new feature
- `fix:` — bug fix
- `refactor:` — code restructuring without behavior change
- `docs:` — documentation changes
- `test:` — adding or updating tests
- `chore:` — build, tooling, config changes
6. Focus the message on **why** not **what** — the diff shows what changed
7. Keep the first line under 72 characters
8. Add a body paragraph if the change is non-trivial
9. Create the commit
Do NOT push unless explicitly asked. Do NOT use `--no-verify` or skip hooks.
$ARGUMENTS
在 GitHub 查看