engineering / Git & commits
commit-conventions
Formats commits as conventional commits and matches commit-message type (feat:, fix:, chore:) to branch intent, appending optional issue references.
Markdown workflowYou or your agent
Put it to work.
Ask your agent to use commit-conventions, or let it load the skill when your task matches the description.
Use the commit-conventions skillInvocation syntax varies by agent. Use the skill name in your prompt, or your agent’s supported slash command.
About this skill
Conventional-commit guidance that keeps commit types aligned with branch intent.
- Branch intent and first commit type should match (
feat,fix,chore) - Supports optional issue references (for example
[ENG-123]) - Keeps commit history reviewable and predictable
Install
bash
npx skills@latest add smeltery/skillsOr copy just this skill:
bash
mkdir -p ~/.claude/skills/commit-conventions
curl -fsSL https://raw.githubusercontent.com/smeltery/skills/main/skills/engineering/commit-conventions/SKILL.md \
-o ~/.claude/skills/commit-conventions/SKILL.mdUsage
Use when preparing commit messages, especially for the first commit on a branch.
Files
SKILL.md— canonical skill definition.
Read the full SKILL.md
Format
Commits should be formatted as conventional commits.
Matching Branch Intent
The first commit should match the branch intent:
| Branch | First Commit |
|---|---|
feat/<feature-name> |
feat: feature name |
fix/<bug-name> |
fix: bug name |
chore/<task-name> |
chore: task name |
Examples
bash
# Feature branch
git commit -m "feat: add user avatar upload"
# Fix branch
git commit -m "fix: resolve plan export timeout"
# Chore branch
git commit -m "chore: update typescript to v5.3"With Issue References
Append issue reference when provided:
bash
git commit -m "feat: add user avatar upload [AI-123]"