Agent skill · software engineering · daymade
github-review-pr
Reviews PRs against the live base with immutable objects and three-way merges. Use for PR review/merge readiness, main changed, closed-PR reconsideration, open-PR sweeps, review-led repair, or explicitly requested independent review of your own contribution. Not for GitHub CRUD (use github-ops), authoring/maintaining your PR (use github-contributor), or merging without fresh review.
Why this skill is useful
Adds specific commands and workflows for reviewing GitHub pull requests that the AI wouldn't reliably generate on its own.
What it needs
Requires github account access. About 11k tokens when loaded. Last updated 2026-08-07. 1,320 stars on the source repository.
What this skill does
Review a Contributor PR as Maintainer Treat every verdict as a claim about exact immutable Git objects. Review each PR's prospective effect on the current base branch, not a stale web diff or an old review snapshot. A queue review is a sequence of independent PR reviews, never one shared approval or mutation batch. Default to read-only. Do not comment, approve, request changes, update the branch, push, close, merge, enable auto-merge, bypass protections, or delete a branch unless the user explicitly authorizes that exact external mutation. Use $ARGUMENTS as the target. Strip the recognized --personal-maintainer and --all-open flags before parsing it. If neither a PR nor an explicit all-open request can be resolved after inspecting the current repository and conversation, ask for the PR URL, owner/repo#number, or confirmation that all open PRs are in scope. Route the Request Use this workflow for any of these: One open GitHub PR when the outcome is review, re-review, merge-readiness, review-led repair, or review-led landing. One explicitly named closed-unmerged PR when the user wants a retrospective merit review, wants to know why it closed, or is considering whether it should stay closed or be reopened. Reopening remains a separate mutation. All currently open contributor PRs in one repository when the user explicitly asks for an open-PR queue review. Process them by createdAt from newest to oldest and issue one evidence ledger and decision per PR. An author's own contribution only when the user explicitly requests an independent maintainer-style evaluation. Apply the same immutable-object and counter-review method in read-only mode; do not switch to personal-maintainer mode, post a formal approval, or acquire merge authority. Return the verdict to the author; authorized repairs remain with github-contributor:github-contributor. Use a narrower workflow instead when the request is only one of these: Create or administer PRs, issues, repositories, or workflows. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/github-review-pr