Conventional Commits helps you write clear, consistent git commit messages and branch names. This skill follows the official v1.0.0 standard. It makes your git history easy to read and understand.
When you use these rules, tools can automatically create changelogs and decide the next version number. Your team will see exactly what each branch and commit does. No more guessing from vague messages.
This skill also shows you how to name worktrees and work with multiple branches at the same time. Anyone who uses git for code projects will benefit from these simple, reliable patterns.
Global
mkdir -p ~/.claude/skills/conventional-gitProject
mkdir -p .claude/skills/conventional-gitSource Repository
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
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
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
Git Commitgithub/awesome-copilot
Automatically write standardized git commits by analyzing your code changes
Git Advanced Workflowswshobson/agents
Master advanced Git workflows for clean history and confident recovery