code-review

Reviews code changes against requirements using structured subagent prompts and severity-ranked feedback.

7|Updated May 13, 2026
One-click install
npx skills add https://github.com/DawnMoon1542/agents-skills --skill code-review-dawnmoon1542
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/DawnMoon1542/agents-skills/tree/main/workflow/code-review
Command: npx skills add https://github.com/DawnMoon1542/agents-skills --skill code-review-dawnmoon1542

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review often degrades into performative agreement or skipped verification. This Skill enforces technical rigor when requesting reviews, responding to reviewer feedback, and dispatching reviewer subagents, so issues are caught before merge and feedback is validated rather than blindly implemented. ## Core Features & Use Cases - Review Triggering Guidance: Defines when to initiate a review (before merge, after complex bug fixes, when stuck) and how to dispatch a review subagent with git SHA ranges. - Feedback Handling Protocol: Provides a structured response pattern for received feedback—read, restate, verify against the codebase, then implement or push back with technical reasoning. - Reviewer Prompt Templates: Includes ready-to-use templates for code quality review and spec-compliance review, with severity classification (Critical/Important/Minor) and merge readiness assessment. - Use Case: Before merging a feature branch, dispatch the spec-compliance reviewer to confirm the implementation matches requirements, then run the code quality reviewer to catch architecture, testing, and error-handling gaps. ## Quick Start Ask the AI to review the changes between the base commit and HEAD against the original plan using the code review skill.

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 changes before merging a branch?

Get the base and head git SHAs, then dispatch a review subagent using the code-reviewer template with a description of what was built and the original requirements. The reviewer returns severity-classified issues and a merge readiness assessment.

How should I respond to code review feedback?

Read the full feedback, restate the technical requirements, verify each point against the actual codebase, then implement valid items one at a time with tests. Push back with technical reasoning when suggestions would break existing functionality or violate YAGNI.

What is the difference between spec review and code quality review?

Spec-compliance review verifies the implementation matches what was requested, catching missing or extra features. Code quality review checks architecture, error handling, and testing. Run spec review first, then quality review.

When should I push back on reviewer feedback?

Push back when a suggestion would break existing functionality, the reviewer lacks full context, it violates YAGNI for unused features, or it conflicts with prior architectural decisions. Use technical reasoning and cite working code or tests.

When should code review be skipped?

Skip it when a workflow like subagent-driven development already includes built-in spec, quality, and final reviews. Never skip because the change seems simple, and never merge with unfixed Critical or Important issues.