code-review

Reviews branch diffs qualitatively against intent, architecture, and ISO/IEC 25010 quality criteria.

Updated May 8, 2026
One-click install
npx skills add https://github.com/juanca202/sdd-devkit --skill code-review-juanca202
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/juanca202/sdd-devkit/tree/main/skills/code-review
Command: npx skills add https://github.com/juanca202/sdd-devkit --skill code-review-juanca202

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Automated checks tell you whether code runs and passes rules, but not whether it solves the right problem or is well designed. This Skill performs a senior-engineer-style qualitative review of a branch's diff against its base, evaluating intent, architecture, and design, and returns actionable findings with severity, a verdict, and next actions. ## Core Features & Use Cases - Three-dimension review: Semantic analysis (does the code match the stated intent from a user story, ticket, or spec), architecture and design evaluation mapped to ISO/IEC 25010 characteristics (maintainability, reliability, security, performance, compatibility), and senior-style actionable feedback explaining the why behind each finding. - Severity-calibrated verdicts: Findings are classified as CRITICAL, MAJOR, MINOR, or SUGGESTION, producing an APPROVED, REJECTED, or INCOMPLETE verdict, with a configurable policy for fixing or justifying blocking findings. - Idempotent reports: Caches the review via a canonical fingerprint of the code plus the base commit, so an unchanged diff returns the existing report instead of re-reviewing; supports scoped modes like working-tree, path-limited scope, and blocking-only. - Use Case: Before opening a pull request, ask for a review of your feature branch against develop. The Skill inspects the full diff including uncommitted changes, checks it against the originating user story's acceptance criteria, flags a layering violation and an N+1 query with concrete suggestions, and writes the verdict report to docs/audits/code-review.md. ## Quick Start Ask the agent to review the code on your current branch against its base before creating the pull request.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a branch diff before creating a pull request?▼

Invoke the code review on your branch against its base; it analyzes the full diff including uncommitted changes across intent, architecture, and feedback dimensions. It returns severity-classified findings with a verdict and writes a report to docs/audits/code-review.md.

What is the difference between code review and quality checks?▼

Code review answers whether the change solves the right problem and is well designed, by reading the diff. Quality checks answer whether the code runs and passes rules, by executing tests, linters, and builds. They are independent gates with separate verdicts.

Can I review only uncommitted changes in the working tree?▼

Yes, the working-tree modifier limits the review to uncommitted changes via git diff HEAD plus relevant untracked files. Scoped reviews do not overwrite the standing branch report and are never served from cache.

Does code review require spec-driven development artifacts?▼

No, plugin artifacts are not required. The change intent can come from a user story or work item, an external ticket or spec, or be inferred from the branch, commits, and PR description. If intent is undeterminable, that dimension is marked not assessed.

Why does a repeated code review return the old report?▼

The review is idempotent: if the code fingerprint and base commit are unchanged and the prior verdict was approved, the existing report is returned. Pass the revalidate modifier to force a fresh review.

When are blocking findings fixed automatically?▼

By default the review pauses and asks whether to correct or justify each blocking finding. Setting verification.codeReview.confirmFix to never in the project settings applies suggested fixes directly without asking, then restarts the review.