⚡AgentSkills
🧭 Engineering Leadership · Open Source Stewardship

Land merged PRs in large OSS repositories

A merge-rate-first contribution workflow: issue selection, minimal diffs, review follow-through. Use when contributing to someone else's repo, opening PRs upstream, or reviving stalled pull requests.

intermediate~30 minEngineering ManagersTech LeadsStaff Engineers

Steps

  1. 1Pick labeled issues with recent maintainer activity; claim in a comment
  2. 2Read CONTRIBUTING.md, AGENTS.md, and ten recent merged commits first
  3. 3Branch per issue; one logical change per PR
  4. 4Include tests matching repo conventions; keep diff reviewable in one sitting
  5. 5Open with Fixes #n, proof of behavior before/after, test output
  6. 6Answer every review comment same-day; ping politely once after two silent weeks

Common Pitfalls

  • ▲Unrequested feature PRs to roadmap items
  • ▲Drive-by reformatting bloating diffs

Commands

Install with skills CLI
$ npx skills add aniruddhaadak80/skills --skill oss-pr-landing
Install globally
$ npx skills add aniruddhaadak80/skills --skill oss-pr-landing -g
Find good first issues
$ gh search issues --repo <owner>/<repo> "good first issue" --state open

Tags

#open-source#pull-requests#contribution#engineering-leadership#open-source-stewardship

Related skills

Triage issues like a sustainable maintainerintermediate

Labels, templates, and response SLAs keeping the queue trustworthy without burnout.

🧭 Engineering Leadership·~30m
Open →