commit
Create conventional commit messages. Use when the user says "commit this", "save changes", "git commit", asks to commit code, write a commit message, or format git history. Follows conventional commits specification.
来源信息
- 仓库
- poteto/noodle
- 最近来源活动
- 2026年3月19日 04:43
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 606
- Forks
- 64
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- commit
- description
- Create conventional commit messages. Use when the user says "commit this", "save changes", "git commit", asks to commit code, write a commit message, or format git history. Follows conventional commits specification.
# Conventional Commits
Follow these project-specific rules when creating commits.
## Branching
**Never create bare branches.** If you need branch isolation, use the `worktree` skill. For simple changes, commit directly on the current branch (including main). Do not run `git checkout -b`.
## Project Rules
- **One commit per logical change** — never combine unrelated fixes or features. Three independent changes = three commits.
- **Only commit files you changed** — never pull in unrelated files from concurrent sessions.
- **Always include a body** — no title-only commits. Explain what and why.
- **`merge` type** — use `merge` (not a merge commit) when merging a worktree or feature branch.
- **Sequence commits** to maximise option value — foundational infrastructure first, then features that build on it.
## Example
```
feat(alerts): Add Slack thread replies for alert updates
When an alert is updated or resolved, post a reply to the original
Slack thread instead of creating a new message. This keeps related
notifications grouped together.
```
## References
- [Conventional Commits Specification](https://www.conventionalcommits.org/en/v1.0.0/#specification)
在 GitHub 查看