Pr Workflow
tursodatabase/tursoThis guide helps you write better commits and pull requests. Each commit should be small and focus on one thing. Do not mix code changes with formatting or refactoring. Use a short message that explains what you did.
Keep your pull requests small and focused. Run tests before you submit. Every commit should tell part of the story. If you use GitHub Actions, be careful with turn limits and avoid rabbit holes.
Never commit secrets, passwords, or .env files. When adding a new dependency, include its license and update your notice file. Always check official docs before guessing API parameters.
Add Pr Workflow skill to your workflow
Global
mkdir -p ~/.claude/skills/pr-workflowProject
mkdir -p .claude/skills/pr-workflowSource 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