Conventional Commit
marcelorodrigo/agent-skillsWriting clear commit messages helps your entire team understand code changes. This guide shows you the conventional commit format. You will learn how to structure each commit the right way.
Each commit needs a type like feat or fix. You can add a scope and a short subject line. This keeps your git history clean and easy to follow.
Use the breaking change marker for big updates. Following these rules makes automatic versioning possible. Your teammates will appreciate clear messages.
Add Conventional Commit skill to your workflow
Global
mkdir -p ~/.claude/skills/conventional-commitProject
mkdir -p .claude/skills/conventional-commitSource Repository
More Git & Pull Requests Claude Code Skills
Caveman Commitjuliusbrussee/caveman
Generate ultra-compressed commit messages with Conventional Commits format
Verification Before Completionobra/superpowers
Always run fresh verification before claiming work is complete or passing
Git Guardrails Claude Codemattpocock/skills
Stop dangerous git commands from running automatically with safety hooks
Setup Pre Commitmattpocock/skills
Automate code formatting type checking and tests before every commit
Using Git Worktreesobra/superpowers
Isolate your feature work with git worktrees and keep your main branch safe
Finishing A Development Branchobra/superpowers
Finish your development branch with merge, pull request, or cleanup options
Resolving Merge Conflictsmattpocock/skills
Resolve Git merge conflicts step by step preserving both intents
Git Commitgithub/awesome-copilot
Automatically write standardized git commits by analyzing your code changes