Conventional Commit
github/awesome-copilotClear commit messages make it easier for your team to understand what changed. This guide helps you write standardized messages using a simple XML format. You get step by step instructions, examples, and validation rules to follow.
You start by checking your changes with git status and git diff. Then you build your message using a structured template with a type, scope, and description. The tool automatically runs the commit command for you.
This workflow is perfect for developers who want consistent commits. It follows the Conventional Commits specification. You will avoid common mistakes and keep your project history clean.
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