code-review

Reviews code implementation against Product-Spec.md and outputs a structured evidence-based review report.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/iJosueeh/amauta --skill code-review-ijosueeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/iJosueeh/amauta/tree/main/.opencode/skills/code-review
Command: npx skills add https://github.com/iJosueeh/amauta --skill code-review-ijosueeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Verifying that implemented code actually matches the product specification is tedious and error-prone; this Skill audits completeness, quality, security, and type safety against Product-Spec.md and design mockups, producing a structured report with file:line evidence for every conclusion. ## Core Features & Use Cases - Spec Compliance Audit: Checks every functional requirement in Product-Spec.md item by item, classifying each as fully, partially, or not implemented, and flags Spec Drift for out-of-scope code. - Multi-Dimension Parallel Review: For moderate or complex changes, dispatches four review dimensions (design, bug, security, types) whose findings are aggregated with confidence scoring and risk ranking. - Evidence-Based Reporting: Every finding includes severity, impact, confidence, risk_rank, and file:line evidence, sorted into Must-fix, Should-fix, and Insight buckets with a final ship/fix-first/blocked verdict. - Use Case: After a development phase completes, run the review to confirm all Spec features exist, catch hardcoded credentials or any type usage, and receive a prioritized fix list before sign-off. ## Quick Start Ask the AI to run /code-review to audit the current codebase against Product-Spec.md and produce an aggregated review report.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review code against a product specification automatically?▼

Run the /code-review command after ensuring Product-Spec.md exists in the project. The skill extracts every functional requirement, locates the corresponding code implementation, and reports each item as fully, partially, or not implemented with file:line evidence.

What does the code review report check for?▼

The report covers functional completeness against the Spec, surgical changes audit, simplicity audit, security patterns (hardcoded credentials, XSS, injection), and type safety issues like any usage or @ts-ignore. Findings are sorted by risk_rank into Must-fix, Should-fix, and Insight buckets.

When does the skill use parallel review agents?▼

Parallel four-dimension review (design, bug, security, types) triggers only for moderate or complex changes, such as multi-module edits, new public APIs, or security-sensitive code. Simple changes like typo fixes default to a quick single-aggregator pass.

Does the code review skill fix the issues it finds?▼

No, the skill's scope ends at outputting the review report. Fixes are routed by the main agent: missing features go to a dev-builder skill, while bug, security, and type issues go to a bug-fixer skill, followed by a re-review.

What files are required before running a code review?▼

Product-Spec.md is required as the comparison baseline; if missing, the skill prompts to generate it first. Optional inputs like DEV-PLAN.md, Design-Brief.md, and design tool MCP access enhance phase checklist and UI consistency verification.