GitHub Contributor

What it does

It walks Claude through the full PR lifecycle in five phases, each with concrete git and gh commands.

• Phase 1 — Discovery: Treats CONTRIBUTING.md as a hard merge contract (AI-contribution clauses, issue-first rules, per-language test commands). Uses gh pr list to measure the project's recent merged-PR size distribution and flags PRs that are 5–10× too large.
• Phase 2 — Implementation: Branch off upstream main, write a one-paragraph scope contract, keep the diff minimal, and use Conventional Commits plus a --fixup/autosquash workflow.
• Phase 3 — Quality gates: Run the project's exact lint/test commands; for Tauri/Electron/desktop apps, isolate the data directory and run real end-to-end verification against persisted state. A self-audit step forces every "I tested…" claim to have evidence.
• Phase 4 — PR description: A full body skeleton (Summary, What, Why, Test Plan, Backward Compatibility, Security, Screenshots, Related Issue, Checklist), a test-coverage matrix table, screenshot strategies that don't pollute the repo, and an AI-assisted disclosure template.
• Phase 5 — Post-submission: Reply to bot review findings inline via gh api ... in_reply_to, rebase safely with --force-with-lease, and filter counter-review noise by probability / cost / scenario.

It also ships ten named anti-patterns and two real case studies in references/.

Who it's for

• First-time open-source contributors who keep getting PRs closed without explanation
• Developers using AI coding tools who need to avoid the "AI dump" reputation hit
• Engineers comfortable with internal PRs but new to external maintainer etiquette
• Anyone who googles rebase-conflict or bot-reply commands every single time

Examples

1. "Open a PR against owner/repo for this fix" — Claude reads CONTRIBUTING.md, benchmarks your diff against recent merges, runs the project's test commands, and drafts an evidence-backed PR body.
2. "Respond to the CodeRabbit review" — Each finding is filtered, then answered inline on the exact line with the commit SHA and the test that resolves it.
3. "My branch conflicts with upstream main" — Fetch, rebase file-by-file, --force-with-lease push, while guarding against pulling unrelated upstream changes into your PR.

Install the skill I found on Claude Skill Mart.
Copy the github-contributor folder from the GitHub repo daymade/claude-code-skills into my ~/.claude/skills/github-contributor/.
When it's done, tell me in one line what this skill can do.