skills.rest
manusco
manuscoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review-pr

Audit pull requests and diffs against a Blocking Registry with findings ranked by user harm.

Updated Dec 1, 2025
Search Tags:#code review#pull request#diff audit#findings ranking#blocking registry#user harm
One-click install
npx skills add https://github.com/manusco/wolfgang --skill review-pr-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/manusco/wolfgang/tree/main/.cursor/skills/review-pr
Command: npx skills add https://github.com/manusco/wolfgang --skill review-pr-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often produce findings ordered by file position rather than actual impact, making it hard to prioritize what truly matters. This Skill audits a PR or diff against a Blocking Registry and ranks findings by user harm so reviewers focus on the most damaging issues first. ## Core Features & Use Cases - Registry-Based Auditing: Checks every PR or diff against the Blocking Registry to catch known blocking issues. - Harm-Ranked Findings: Orders review findings by user harm instead of file order for faster triage. - Delegated Procedure: Routes the /review-pr command to the reviewer procedure defined in .agents/skills/ops/reviewer/SKILL.md and follows its Definition of Done. - Use Case: Before merging a large feature branch, run the review to surface blocking issues ranked by severity so the team fixes the highest-harm problems first. ## Quick Start Ask the assistant to run /review-pr on the current pull request to audit it against the Blocking Registry and return findings ranked by user harm.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I review a pull request for blocking issues?▼

Run the /review-pr command on the PR or diff. The Skill audits the changes against the Blocking Registry and returns findings ranked by user harm rather than file order, so the most damaging issues appear first.

How are code review findings ranked in this review process?▼

Findings are ranked by user harm, not by file order. This prioritization ensures reviewers address the issues with the greatest impact on end users before less critical ones.

What is the Blocking Registry in PR review?▼

The Blocking Registry is the reference set of known blocking issues that the PR or diff is audited against. The review procedure defined in .agents/skills/ops/reviewer/SKILL.md governs how the registry is applied.

Does this Skill contain the full review procedure itself?▼

No. This Skill only routes the /review-pr command to the reviewer procedure located at .agents/skills/ops/reviewer/SKILL.md, which must be read in full and executed according to its Definition of Done.

When should I not rely on this PR review approach?▼

Avoid relying on it when the reviewer procedure file at .agents/skills/ops/reviewer/SKILL.md is missing or outdated, since this Skill only routes to that procedure and contains no standalone review logic.

Related Skills

Explore More Software Engineering Skills→
dhar174dhar174
1

create-github-pull-request-from-specification

Create and update GitHub pull requests from specification files.

Community
Intermediate
FastLEDFastLED
7.5k

address-reviews

Fetch, classify, fix, and reply to CodeRabbit review comments on GitHub pull requests.

Official
Intermediate
arndvsarndvs

pr-preflight

Audits changed files, diffs, and stack tooling before opening a pull request.

Community
Advanced
Let-s-internLet-s-intern
8

code-review

Review code changes across pull requests and local git diffs.

Official
Advanced