skill-reviewing-pull-requests

Inspects pull requests and returns verdicts bound to the exact reviewed head SHA.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/longdang193/project-OS-starter --skill skill-reviewing-pull-requests-longdang193
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-reviewing-pull-requests
Source: https://github.com/longdang193/project-OS-starter/tree/main/generated_agents/claude/skills/skill-reviewing-pull-requests
Command: npx skills add https://github.com/longdang193/project-OS-starter --skill skill-reviewing-pull-requests-longdang193

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-agent development needs independent pull request review evidence that stays valid only for the exact commits inspected, preventing stale approvals and unverified acceptance. ## Core Features & Use Cases - Head-Bound Review Evidence: Verifies repository identity, base ref, head ref, and expected head SHA before inspection, returning BLOCKED when the current head differs from the expected head. - Structured Verdicts: Returns PASS, FAIL, or BLOCKED verdicts covering diff scope, tests, required checks, security risks, approved deviations, and known limits. - GitHub Review State Handling: Submits GitHub APPROVE only when reviewer identity is eligible and distinct from the PR author, otherwise submits COMMENT or no action. - Use Case: A lead controller dispatches an independent agent to review PR #42 against an approved scope; the agent inspects the exact diff at the expected head SHA and returns signed review evidence that new commits automatically invalidate. ## Quick Start Review pull request 42 in this repository against base main and the expected head SHA, then return the Project OS verdict with full review evidence.

Frequently Asked Questions about skill-reviewing-pull-requests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request with an independent agent?▼

Provide the repository, PR number, base ref, head ref, expected head SHA, approved scope, and required checks. The agent inspects the exact diff and returns a PASS, FAIL, or BLOCKED verdict with structured review evidence.

What happens when new commits are pushed during pull request review?▼

New commits invalidate prior review evidence. If the current PR head differs from the expected head SHA, the review returns BLOCKED and must rerun against the updated head before any verdict is accepted.

Can an AI agent approve a pull request on GitHub?▼

The agent submits GitHub APPROVE only when its reviewer identity is eligible, differs from the PR author when required, and repository rules allow the approval to count. Otherwise it submits COMMENT or takes no GitHub action.

Does CI passing count as pull request approval?▼

No. Approval is never inferred from CI alone. The review inspects the diff, changed-file scope, tests, required checks, and security or data-loss risks, and records known limits and unverified claims.

What are the limitations of automated pull request review?▼

The review does not implement fixes, merge, delete branches, remove worktrees, or decide task acceptance. It returns BLOCKED when identity, access, required proof, or review prerequisites are unavailable.