04-review

Review implementation diffs across correctness, readability, architecture, security, and performance.

29|2|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/leing2021/super-pi --skill 04-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 04-review
Source: https://github.com/leing2021/super-pi/tree/main/skills/04-review
Command: npx skills add https://github.com/leing2021/super-pi --skill 04-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you catch bugs, design issues, and risky changes by reviewing code evidence against the implementation diff, the prior plan artifacts, and existing solution patterns before you commit.

Core Features & Use Cases

  • Five-axis, evidence-first review: Produces structured findings (with severity, evidence, and recommended action) instead of vague opinions.
  • Diff-aware reviewer routing: Selects the right reviewer personas based on the change scope and diff metadata via review_router.
  • Plan + prior learnings awareness: Loads relevant plan artifacts when present and searches docs/solutions/ for related solution evidence.
  • Autofix loop with re-review: Applies autofixable findings and re-reviews changed lines (up to 3 iterations).
  • Optional browser QA mode: After review, can continue into browser-based QA (agent-browser) for visual/functional/UX issues and optionally add regression tests.

Quick Start

Use the 04-review skill after you finish implementing changes and want a structured, evidence-first review before committing.

Frequently Asked Questions about 04-review

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

FAQPage Schema
How do I run an evidence-first code review on a diff before committing?

To run an evidence-first code review, you provide your implementation diff and optional plan artifacts. The review loads layered rules, searches solution patterns, and emits structured findings with severity, evidence, and recommended actions.

What does an evidence-first code review check for?

An evidence-first code review checks your diff across five axes: correctness, readability, architecture, security, and performance. It selects reviewer personas based on change scope and diff metadata to produce targeted findings instead of vague opinions.

Can I automatically fix code issues found during a security review?

Yes, an autofix-and-re-review loop applies autofixable findings and re-reviews the changed lines. This automated review loop supports up to three iterations to ensure your code meets the required standards before final decisions.

Does the code review workflow support browser-based QA testing?

Yes, after the initial code review, the workflow can continue into a browser QA mode. This mode uses agent-browser to identify visual, functional, and UX issues, and can optionally add regression tests for your implementation.

Do I need a TDD workflow or plan artifact to use this code review skill?

No, plan artifacts are optional but enhance the review's context awareness. The skill loads relevant plan artifacts when present and searches existing solution directories for related evidence to improve finding accuracy.