pr-review

Validate pull requests against original requirements and route out-of-scope findings to GitHub issues.

326|35|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/athola/claude-night-market --skill pr-review-athola
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/athola/claude-night-market/tree/main/plugins/sanctum/skills/pr-review
Command: npx skills add https://github.com/athola/claude-night-market --skill pr-review-athola

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sanctum:shared, sanctum:git-workspace-review, pensive:unified-review, imbue:evidence-logging, and includes scripts (resource) and references (resource) components.

What problem does it solve?

PR review focused on ensuring the implementation aligns with original requirements and surfaces out-of-scope work as backlog items.

Core Features & Use Cases

  • Scope baseline establishment and change tracing
  • Classification of findings (BLOCKING, IN-SCOPE, BACKLOG, etc.)
  • Backlog triage and GitHub integration

Quick Start

Run a scope-focused PR review and route out-of-scope concerns to GitHub issues.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I perform scope-focused code reviews on pull requests?

Scope-focused PR reviews validate that implementation aligns with original requirements by establishing a baseline, gathering changes, validating against requirements, classifying findings (BLOCKING, IN-SCOPE, BACKLOG, SUGGESTION, IGNORE), and routing out-of-scope work to GitHub issues before merging.

How do I prevent overengineering by identifying out-of-scope work in PRs?

Route out-of-scope findings discovered during PR review directly to GitHub issues for backlog triage, keeping feature branches focused on original requirements and separating requirement-compliant changes from additional work.

Can I integrate PR reviews with GitHub issue tracking and backlog management?

Yes, the Skill integrates with GitHub to automatically classify PR findings and create backlog items, connecting code reviews to requirement-compliance validation across plan, spec, and task documents.

What's the difference between scope-focused and standard code review?

Scope-focused review traces changes against original requirements and classifies findings by scope impact, whereas standard code review typically checks quality alone. This approach surfaces overengineering and requirement gaps systematically.

When should I use scope-focused PR reviews in my workflow?

Apply scope-focused reviews before merging feature branches, during backlog triage to validate requirements compliance, and when preventing overengineering is critical to maintaining project scope boundaries.

Does this work with existing GitHub workflows and code review processes?

Yes, scope-focused PR reviews integrate into existing GitHub workflows by working alongside standard code review, adding requirement-compliance classification and automated backlog routing before merge.