Planning an open source contribution can feel overwhelming. This skill helps you create a clear and actionable plan before you start coding. It takes the output from research and turns it into a step-by-step strategy.
You will define the scope of your change, pick the right issue to target, and write acceptance criteria from the maintainer's view. The plan also includes a risk assessment and an implementation approach. This makes your pull request more likely to be accepted.
Use this skill after you have researched the repository but before you write any code. It works best for non-trivial changes that need careful planning. The output is a markdown file you can follow as you work.
Global
mkdir -p ~/.claude/skills/pr-planProject
mkdir -p .claude/skills/pr-planSource 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