code-review

Reviews code changes by running linters, formatters, and tests, then reporting labeled findings without editing code.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/thedutchvisiongroup/agent-skills --skill code-review-thedutchvisiongroup
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/thedutchvisiongroup/agent-skills/tree/main/skills/code-review
Command: npx skills add https://github.com/thedutchvisiongroup/agent-skills --skill code-review-thedutchvisiongroup

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes references (resource) components.

What problem does it solve? Code reviews that only skim a diff miss logic errors, dead code, and design problems. This Skill enforces a systematic six-phase review process that always runs the project's linters, formatters, and test suite before analyzing logic, design, complexity, naming, performance, and documentation — while never modifying the code under review. ## Core Features & Use Cases - Mandatory automated verification: Detects project tooling from config files and CI, runs lint, type checks, format checks, and the full test suite, and reports every issue without fixing anything. - Structured design and logic analysis: Checks DRY, SOLID, YAGNI, complexity, naming, dead code, performance patterns (N+1, O(n²)), and documentation using dedicated reference guides. - Labeled advisory report: Delivers findings with Conventional Comments labels (issue, suggestion, nitpick, question, praise) and an advisory verdict of APPROVE, COMMENT, or REQUEST CHANGES. - Use Case: Before merging a pull request that touches payment logic, ask for a review. The Skill runs the test suite, flags a sensitive payment path, recommends a separate security-review agent, and hands test-quality assessment off to the test-driven-development skill. ## Quick Start Review the changes in this pull request: run the linter and tests, check the logic and design, and give me a labeled findings report with a verdict.

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 pull request with an AI code reviewer?ā–¼

Provide the changed files or diff and ask for a review. The Skill first runs the project's linters, formatters, and tests, then analyzes logic, design, complexity, naming, dead code, performance, and documentation, delivering a labeled findings report with an advisory verdict.

What does an automated code review check besides tests?ā–¼

Beyond running the test suite, it checks logic errors (off-by-one, null handling, race conditions), error handling, DRY/SOLID/YAGNI design principles, complexity, naming, dead code, performance patterns like N+1 queries, and documentation completeness.

Does the code review skill fix the issues it finds?ā–¼

No. The reviewer is strictly advisory-only and never edits, fixes, or reformats code. It reports findings with file locations, rationale, and recommendations; any fix is treated as a separate task after the review is delivered.

Does this code review cover security vulnerabilities?ā–¼

No, security review is explicitly out of scope. The Skill detects sensitive paths like authentication, payments, and secrets, then recommends starting a separate security-review agent rather than analyzing vulnerabilities itself.

When should I not use an automated code review?ā–¼

Skip it for formatting-only changes, generated code, vendor libraries, and documentation-only edits. Test-suite quality reviews belong to the test-driven-development skill, and security audits belong to a dedicated security-review agent.