Agent skill · writing content · daymade
github-contributor
Ships pull requests to open-source projects you don't maintain — CONTRIBUTING compliance, PR-size/scope checks, minimal-diff implementation, AI-disclosure PR descriptions, and rebase or bot-review replies. Use for 提 PR / 上游 PR / 贡献代码, "open a PR", "fix this upstream", "rebase against main", "respond to the bot review". Not for reviewing PRs as maintainer (use github-review-pr) or general GitHub CRUD (use github-ops).
Why this skill is useful
Provides a structured playbook for navigating the PR process in open-source projects, including specific commands and compliance checks that the AI wouldn't reliably generate on its own.
What it needs
About 11k tokens when loaded. Last updated 2026-08-07. 1,320 stars on the source repository.
What this skill does
GitHub Contributor A phase-based playbook for shipping pull requests that maintainers actually want to merge. The skill is structured around the real PR lifecycle — discovery → implementation → quality gates → description → post-submission — because each phase has its own failure modes and the most common mistake is doing the right thing at the wrong phase (e.g., writing the perfect description for a PR that's 10× too large). Phase 0 — When to use this skill Use this skill when all of these are true: You are contributing to a repo you do not maintain (the maintainer can close your PR without explanation). The work touches one or more of: source code, tests, docs, build config. You want the PR merged, not just submitted. Do not use this for: your own repos, internal team PRs with shared context, hot-fix branches where a maintainer is waiting on you, or trivial single-line changes (one comment is enough). Phase 1 — Pre-PR Discovery The most common reason PRs get closed is a mismatch between what the contributor assumes is acceptable and what the maintainer has already written down. Solve this before writing code. Step 1.1 — Read CONTRIBUTING.md as a hard contract CONTRIBUTING.md is not style advice. Treat every numbered rule as a precondition for merge. Pay special attention to: AI-assisted contribution clauses. Many projects added these in 2024-2026 after the AI PR wave. Typical phrasing: "AI-generated PRs without prior discussion may be closed", "you must be able to explain every line", "one issue, one PR". If this clause exists, you owe the project explicit disclosure (see Phase 4) and you must keep the PR small. Issue-first rules. Some projects require a feature-request issue to exist before any feature PR is opened. Per-language test commands. If CONTRIBUTING.md says pnpm test:unit && cargo test, those are the commands you run, not whatever your IDE prefers. If CONTRIBUTING.md is missing, that itself is a red flag — see references/projectevaluation.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/github-contributor