Writing clear commit messages is a key part of working on a team project. This helper tool guides you step by step to create commits and pull requests that follow CockroachDB rules. It helps you keep your version history neat and easy to understand.
The process starts with analyzing your changes using git diff. Then you identify the affected package. You are asked for an issue number and if release notes are needed. The tool helps you write a short subject line and a detailed body. Finally it adds the release note with the right category like bug fix or performance improvement.
Using this skill makes code reviews faster and prevents confusion. Your team will know exactly what changed and why. It is ideal for anyone contributing to CockroachDB projects.
Global
mkdir -p ~/.claude/skills/commit-helperProject
mkdir -p .claude/skills/commit-helperSource 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
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