Individual skill
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).
github-contributor/SKILL.md
Source commit 7c4d326ddd94d504e00e241ba49498e95160afbe
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,522
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- legal Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesSKILL.mdcore · 20,450 bytesreferences/case_study_cc-switch_pr_1624.mddoc · 7,064 bytesreferences/case_study_cc-switch_pr_2634.mddoc · 14,784 bytesreferences/communication_templates.mddoc · 5,410 bytesreferences/high_quality_pr_case_study.mddoc · 8,187 bytesreferences/phase1_discovery.mddoc · 7,316 bytesreferences/phase2_implementation.mddoc · 8,755 bytesreferences/phase3_quality_gates_and_e2e.mddoc · 12,002 bytesreferences/phase4_pr_description.mddoc · 9,281 bytesreferences/phase5_post_submission.mddoc · 9,349 bytesreferences/pr_checklist.mddoc · 7,011 bytesreferences/project_evaluation.mddoc · 3,337 bytesreferences/push_time_gotchas.mddoc · 3,099 bytes
Read excerpt
# 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).
