Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

GitHub Maintainer PR Review

A rigorous maintainer-grade workflow that re-reviews GitHub pull requests against the current base branch, binding every verdict to exact Git OIDs.

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

What it does

  • Keeps three identities separate — the PR-recorded base OID, the live base branch OID, and the PR head OID — so a stale web diff never drives the verdict.
  • Computes the actual prospective landing result with git merge-tree, exposing conflicts, no-ops, and superseded PRs.
  • Detects force-pushes, rewritten history, and polluted branches, then projects only the verified contribution onto the current base for a fair evaluation.
  • Labels every finding with ownership (PR/BASE/SHARED), severity (P0–P2), evidence, and a falsifier or reproduction path.
  • Ends with exactly one decision: LAND_AS_IS, FIX_ON_PR_THEN_LAND, REQUEST_CONTRIBUTOR_CHANGES, DECLINE, CLOSE_AS_SUPERSEDED, COMMENT_ONLY, or BLOCKED.
  • Defaults to read-only: no comments, approvals, merges, or branch deletions without explicit authorization, and untrusted tests run in an isolated clone.

Who it's for

  • Open-source maintainers triaging a backlog of contributor PRs.
  • Tech leads who need to know whether an old review still holds after main moved.
  • Developers who want to evaluate untrusted external code without exposing local secrets or touching their worktree.

Example uses

  1. github-review-pr https://github.com/org/repo/pull/123 — get a findings-first report with the merge result, conflicting paths, and test outcomes tied to the reviewed commit.
  2. "main changed, review again" — prior findings are re-classified as OPEN/FIXED/OBSOLETE/REATTRIBUTED with base-drift effects explained.
  3. github-review-pr --all-open — sweep every open PR newest to oldest, with an independent decision per PR plus a summary table.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/daymade/claude-code-skills/HEAD/github-review-pr/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

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. Check that GitHub CLI is installed: run gh --version (install from https://cli.github.com if missing).
  2. Confirm you are logged in: gh auth status, and run gh auth login if not.
  3. Clone the repository: git clone https://github.com/daymade/claude-code-skills.git
  4. Copy the skill folder: mkdir -p ~/.claude/skills && cp -r claude-code-skills/github-review-pr ~/.claude/skills/
  5. Verify the bundled references/ files came along: ls ~/.claude/skills/github-review-pr
  6. Restart Claude Code, then paste a PR URL and ask it to "review this PR as maintainer" (add --personal-maintainer only if you keep your own maintainer profile file).
View source on GitHub ↗License: MIT