Open-source projects rely on contributions from people like you. But getting a pull request accepted can be tricky. This guide walks you through every step from finding a project to getting your code merged. It covers discovery, implementation, and how to talk to maintainers. You will learn how to keep your changes small and clear. The goal is to make your pull request one that maintainers want to merge.
Before you write any code, the guide teaches you to check the project's rules. You read the CONTRIBUTING.md file as a hard contract. You also check how big recent merged pull requests were. This stops you from wasting time on a change that is too large or against the rules.
You also create a scope contract to keep your work focused. When you implement, you follow a disciplined branch and diff strategy. After submission, the guide helps you respond to reviews and resolve conflicts. This playbook saves you from the most common mistakes that cause pull requests to be closed.
Global
mkdir -p ~/.claude/skills/github-contributorProject
mkdir -p .claude/skills/github-contributorSource 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