Commit
Create conventional commit messages.
by poteto · MIT
The skill
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.
mergetype — usemerge(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
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: poteto/commit-93583873949.
Details
- Publisher
- poteto
- Category
- Software Development › Source control & code review
- License
- MIT
- Updated
- 2026-03-19
References
More from poteto
- Adversarial Review Adversarial code review using cross-model approach.
- Ast Grep Structural code search via ast-grep — use when code shape and element relationships matter, not j…
- Brain Read/write brain files (Obsidian vault at brain/).
- Codex Run Codex CLI (exec, resume) for parallel work, delegating tasks to another model, or background…