4r-review

Reviews code diffs using a risk-tiered four-lens protocol with corroboration and optional ledgers.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill 4r-review-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 4r-review
Source: https://github.com/nico0695/ai-tools/tree/main/skills/generic-skills/4r-review
Command: npx skills add https://github.com/nico0695/ai-tools --skill 4r-review-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code reviews often apply the same shallow effort to every change, missing severe defects in risky diffs while wasting time on trivial ones. This Skill sizes the review to the actual risk of the target and produces evidence-backed findings without ever modifying your code. ## Core Features & Use Cases - Risk-Tiered Triage: Classifies the frozen target as trivial, standard, or full-4r, applying zero, one, or all four lenses (Risk, Readability, Reliability, Resilience) accordingly. - Evidence-Backed Findings: Lens workers return structured findings with severity, evidence class, and causal disposition; only introduced or worsened BLOCKER/CRITICAL defects can block. - Refutation and Fix Rounds: Full-4r reviews run one refuter pass to corroborate or refute inferential severe findings, with up to two scoped fix re-review rounds. - Use Case: Before merging a branch that touches authentication logic, ask for a 4R review; the Skill freezes the diff, runs all four lenses plus a refuter pass, and reports a verdict with an optional persisted ledger at docs/reviews/. ## Quick Start Ask the assistant to run a 4r-review on the current branch changes before merging.

Frequently Asked Questions about 4r-review

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

FAQPage Schema
How do I run a 4R code review on my changes?▼

Explicitly request a 4r-review and optionally name a target such as commits, a range, a branch, a PR, or paths. Without a named target, the Skill reviews uncommitted changes or the current branch against its base, freezing an immutable reference first.

What are the four lenses in a 4R review?▼

The four lenses are R1 Risk (security and stability), R2 Readability (maintainability), R3 Reliability (correctness and testing), and R4 Resilience (recovery and observability). Standard reviews use exactly one lens chosen by the dominant risk signal; full-4r reviews use all four.

When does a 4R review trigger the full four-lens mode?▼

Full-4r applies when the diff touches auth, security, payments, sensitive data, or migrations, or exceeds 400 changed lines. It runs all four lenses plus exactly one refuter pass over severe inferential findings.

Does the 4R review skill modify or fix my code?▼

No, the Skill is strictly read-only and never edits code, tests, or configs. It describes suggested fixes in the report and can show minimal before/after snippets on request, but only the user applies changes.

Which findings can block a change in a 4R review?▼

Only BLOCKER and CRITICAL findings with causal_disposition of introduced, behavior-activated, or worsened can block. WARNING and SUGGESTION rows become info entries, and pre-existing or unknown findings are reported but never block.

Can I persist 4R review results for later re-review?▼

Yes, after the report you can opt in to saving a review ledger at docs/reviews/{target-slug}.md in English. The ledger records findings, corroboration outcomes, and up to two scoped fix rounds against the frozen reference.