review-work

Review code changes and pull requests for supported defects, scope gaps, and merge risk.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill review-work-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-work
Source: https://github.com/pnewsam/skills/tree/main/registry/review-work
Command: npx skills add https://github.com/pnewsam/skills --skill review-work-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code reviews often miss defects that live outside the changed lines, wave off missing test coverage, or produce unsupported findings. This Skill applies a disciplined, evidence-based review process to local changes, artifacts, or existing pull requests so every reported finding is backed by verifiable support. ## Core Features & Use Cases - Evidence-based defect detection: Reads the diff, work record, ticket, and acceptance criteria, then traces outward to consumers of changed contracts across repositories to find real breakage. - Structured review output: Produces a verdict (APPROVE, REQUEST CHANGES, COMMENT), severity-ordered findings, and an honest validation record following a defined output template. - Independent second-pass review: Supports a context-isolated re-review, optionally by a different model family, tasked with refuting standing findings as well as surfacing missed ones. - Merge risk assessment: Evaluates blast radius, security, data integrity, verification, dependencies, and infrastructure to produce a Low-to-Critical risk rating. - Use Case: Given an open pull request, review the diff against the linked ticket's acceptance criteria, triage existing review feedback as supported, fixed, or outdated, and return a verdict with severity-ordered findings. ## Quick Start Use review-work to review the current pull request against its ticket acceptance criteria and report supported findings with a verdict.

Frequently Asked Questions about review-work

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

FAQPage Schema
How do I review a pull request for defects beyond the changed lines?▼

Review the diff for local correctness, then trace outward to every consumer of changed contracts, including other repositories. Verify each acceptance criterion from the linked ticket and check that relied-upon behaviors are pinned by tests that fail on regression.

How do I triage existing review feedback on a pull request?▼

Mark each existing feedback item as supported, fixed, duplicate, outdated, unsubstantiated, or deferred. Verify any item marked fixed against the current candidate rather than trusting prior claims.

Can this review changes that are not in a pull request yet?▼

Yes, a pull request is optional input, not a prerequisite. The review applies to local changes or any artifact, evaluated against its intended outcome and work record.

Does the review skill post comments or merge pull requests automatically?▼

No, it is read-only by default. Posting reviews, replies, resolutions, and merges each require separate authorization and go through the deliver-work skill.

When should a second independent review pass be used?▼

Use a second context-isolated pass for consequential changes, since a single pass both under-finds and over-holds. The second reviewer refutes standing findings and surfaces missed ones, preferably from a different model family.

How is pull request merge risk assessed?▼

Risk is rated Low, Medium, High, or Critical across dimensions including blast radius, change type, security, data integrity, verification, dependencies, and infrastructure. The highest credible single-dimension level anchors the rating, calibrated by mitigations and confidence.