review-work

Reviews uncommitted changes and pull requests with evidence-based severity-ranked findings.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Claudfather/clauDNA --skill review-work-claudfather
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-work
Source: https://github.com/Claudfather/clauDNA/tree/main/skills/review-work
Command: npx skills add https://github.com/Claudfather/clauDNA --skill review-work-claudfather

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review often degrades into rubber-stamping — approvals given on visual inspection without running tests, checking CI, or tracing logic. This Skill enforces a verification-first review discipline so findings are grounded in evidence before anything lands. ## Core Features & Use Cases - Three review modes: changes reviews uncommitted local work before committing, pr reviews a single pull request before merging, and multi-pr fans out parallel subagent reviews across several PRs with cross-PR findings and merge-order recommendations. - Severity-ranked findings: Every issue is categorized as Blocker, Suggestion, Nit, or Question with concrete fixes and file:line references, evaluated across ten dimensions including correctness, security, and error handling. - Anti-rationalization gates: Hard gates block approval until verification commands have been run, and a red-flags checklist catches excuses like "tests probably pass" or "it's just a refactor." - Use Case: Before merging a teammate's PR, run the pr mode to fetch the diff via gh, review it against the dimension checklist, and post a gated gh pr review only after your approval. ## Quick Start Ask the AI to review the current uncommitted changes or a specific pull request, for example by saying "review PR #42 before I merge it."

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 GitHub pull request with AI before merging?

Invoke the pr mode with a PR number or URL. The skill fetches the diff with gh pr diff, reads surrounding context, reviews across ten dimensions, and presents severity-ranked findings before optionally posting via gh pr review.

How do I review uncommitted changes before committing?

Use the changes mode, which runs git status and git diff, analyzes each modified file for correctness and security, and requires verification commands like tests and linters to run before any positive assessment.

Can I review multiple pull requests in parallel?

Yes, the multi-pr mode dispatches one subagent per PR in parallel, then aggregates per-PR verdicts, cross-PR findings like shared root causes and conflicting changes, and a merge-order recommendation. Sets above five PRs are batched.

Does this skill require the GitHub CLI?

The pr and multi-pr modes require the gh CLI for fetching PR diffs, metadata, and posting reviews. The changes mode works with git alone and needs no additional tooling.

When should I not use automated PR review?

Cross-repository PR sets are out of scope, and the skill never merges PRs or approves without verified evidence. Headless contexts cannot clear the posting gate, so reviews stay local there.