A pull request is how you share your code changes with your team. This guide helps you create a proper pull request every time. It follows the rules and templates your project already has. Never push to the main branch – that is the most important rule.
The guide checks your current branch and makes sure you are on a safe one. It runs a preflight check to catch errors before you submit. Then it reads your project's template and helps you write a clear description. Finally it uses the gh CLI to create the pull request. This keeps your team's workflow smooth and consistent.
Global
mkdir -p ~/.claude/skills/pr-creatorProject
mkdir -p .claude/skills/pr-creatorSource 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