Claude Skill MartBrowse skillsWhat is a Skill?
 
← Back to list

GitHub Maintainer PR Review

A maintainer-grade PR review workflow that judges contributor PRs by the real merge result against the current base branch, not a stale web diff.

Dev & CodingAdvanced★ 1,323⑂ 212AI score 8/10Last updated: Aug 8, 2026

What it does

Reviews a single contributor pull request — or a bounded newest-to-oldest sweep of every open PR — from a repository maintainer's perspective, treating every verdict as a claim about exact immutable Git objects.

  • Keeps three identities separate: the PR-recorded base OID, the live base branch OID, and the PR head OID.
  • Computes the actual prospective landing result with git merge-tree, plus the raw base-vs-head tree diff and an isolated projection of the contributor's real changes.
  • Handles base drift, force-pushed/rewritten history, and polluted stale forks without misattributing base commits to the contributor.
  • Labels every finding PR, BASE, or SHARED with P0–P2 severity, so contributors are never blocked for pre-existing base defects.
  • Runs hosted checks and repository tests inside an isolated temporary clone with secrets kept away from untrusted code.
  • Ends with exactly one decision: LAND_AS_IS, FIX_ON_PR_THEN_LAND, REQUEST_CONTRIBUTOR_CHANGES, DECLINE, CLOSE_AS_SUPERSEDED, COMMENT_ONLY, or BLOCKED.

Read-only by default — no comments, approvals, pushes, or merges without explicit authorization.

Who it's for

  • Open-source maintainers with a backlog of external contributor PRs
  • Tech leads on fast-moving repos where main drifts and old reviews go stale
  • Security-conscious teams that must run untrusted fork tests safely
  • Reviewers who want merge readiness backed by evidence, not a green GitHub badge

Examples

  1. Re-review after base drift — "main changed, review https://github.com/org/repo/pull/128 again" → prior findings are marked OPEN/FIXED/OBSOLETE/REATTRIBUTED and the landing diff is recomputed against the live base.
  2. Open-PR queue sweep — run with --all-open to get an independent evidence ledger and decision per PR, followed by a newest-to-oldest summary table with next owner and smallest next action.
  3. Retrospective on a closed PR — "why did org/repo#57 close, should it be reopened?" → the timeline reveals the real closing actor and time, so a contributor self-close is never reported as maintainer rejection.

· · · Install guide · · ·

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

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

Install with a command instead

git clone https://github.com/daymade/claude-code-skills.git && mkdir -p ~/.claude/skills && cp -r claude-code-skills/github-review-pr ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Install the GitHub CLI and authenticate: gh auth login (verify with gh auth status).
  2. Create the skills directory: mkdir -p ~/.claude/skills
  3. Clone the repository: git clone https://github.com/daymade/claude-code-skills.git
  4. Copy the skill: cp -r claude-code-skills/github-review-pr ~/.claude/skills/
  5. Confirm the references/ files (personal_maintainer_context.md, remediation_and_landing.md) came along.
  6. Restart Claude Code, open the target repository, and ask: "Review this PR as maintainer: <PR URL>".
  7. Add --personal-maintainer to apply your own maintainer policy overlay, or --all-open for a full open-PR queue review.
View source on GitHub ↗License: MIT