piv-review-pr

Reviews GitHub pull requests with fresh-eyes analysis, severity triage, and posted verdicts.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill piv-review-pr-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: piv-review-pr
Source: https://github.com/az9713/claude-code-hooks-tutorial/tree/main/skills/.claude/skills/piv-review-pr
Command: npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill piv-review-pr-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code written by an AI session is often reviewed by the same session, which rationalizes its own choices instead of scrutinizing them. This Skill runs a full pull-request review in a clean context — fetching the PR, running the project's validation suite, analyzing the diff, categorizing issues by severity, and posting an approve / request-changes / comment verdict to GitHub — so a human receives a triaged, validated PR to make the final call. ## Core Features & Use Cases - Fresh-eyes diff review: Dispatches a code-reviewer subagent (or reviews in a clean session) covering correctness, type safety, security, performance, tests, and standards compliance, reporting high-confidence issues only. - Validation gate: Runs the project's real test, type-check, lint, and build commands and treats a red suite as a finding in itself. - Severity triage and GitHub posting: Categorizes every issue as Critical / High / Medium / Low, writes a report to .claude/code-reviews/pr-{N}-review.md, and posts it via gh pr review. - Use Case: After piv-create-pr opens a PR, run this Skill on the PR number to get a documented, severity-ranked review posted to GitHub before a human merges. ## Quick Start Ask the agent to review pull request number 42 and post the verdict to GitHub.

Frequently Asked Questions about piv-review-pr

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

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

Provide a PR number, URL, or branch name; the Skill resolves it with gh pr view and gh pr diff, checks out the PR, runs validation, and reviews every changed file in full. It then posts the verdict using gh pr review with approve, request-changes, or comment.

How does automated code review categorize issues by severity?▼

Issues are classified as Critical (security, data loss, crashes), High (type-safety holes, logic errors), Medium (pattern inconsistencies, undocumented deviations), or Low (suggestions). Approval requires no unresolved Critical or High issues plus passing validation.

Can the review run on draft or merged pull requests?▼

Merged or closed PRs stop immediately with nothing to review. Draft PRs are reviewed for direction only and receive a comment rather than an approve or request-changes verdict.

Why review code in a clean context instead of the authoring session?▼

The session that wrote the code tends to rationalize its own decisions instead of scrutinizing them. A clean context or a dedicated code-reviewer subagent provides fresh eyes, which is the core mechanism for catching issues the author missed.

What are the limitations of an agentic PR review gate?▼

It does not replace human review; it produces a validated, triaged PR for a human to approve. It depends on the project's validation suite and standards documents, and documented intentional deviations are not flagged as issues.