Requesting Code Review

Dispatches a code-reviewer subagent to review git changes against plans or requirements.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/dallascrilley/dowser --skill requesting-code-review-dallascrilley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Requesting Code Review
Source: https://github.com/dallascrilley/dowser/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/dallascrilley/dowser --skill requesting-code-review-dallascrilley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often ship with undetected bugs, architecture flaws, or unmet requirements because developers skip structured review. This Skill enforces early, frequent review by dispatching a dedicated code-reviewer subagent that compares implementation against the plan before issues cascade. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a code-reviewer subagent with a structured template covering code quality, architecture, testing, and requirements compliance. - Severity-Categorized Feedback: Returns issues classified as Critical, Important, or Minor with file:line references and a clear merge-readiness verdict. - Workflow Integration: Fits subagent-driven development, plan execution, and ad-hoc development, with defined triggers like after each task or before merging. - Use Case: After completing a task in a multi-step plan, capture the base and head git SHAs, dispatch the reviewer with what was implemented and the requirements, then fix Critical and Important issues before moving to the next task. ## Quick Start Ask the AI to request a code review of the changes you just implemented against the task requirements before proceeding to the next task.

Frequently Asked Questions about Requesting Code Review

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

FAQPage Schema
How do I request a code review of my implementation?▼

Capture the base and head git SHAs for your change range, then dispatch a code-reviewer subagent with what was implemented, the plan or requirements, and the SHAs. The subagent returns categorized issues and a merge-readiness verdict.

When should I request a code review during development?▼

Request review after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also valuable when stuck, before refactoring, or after fixing a complex bug.

What does the code reviewer check in its review?▼

The reviewer checks code quality, architecture, testing coverage, and requirements compliance using a structured checklist. It examines the git diff between the provided base and head SHAs and categorizes findings as Critical, Important, or Minor.

What should I do if the code reviewer is wrong?▼

Push back with technical reasoning rather than accepting incorrect feedback. Show code or tests that prove the implementation works, and request clarification on the reviewer's concern.

Can I skip code review for simple changes?▼

No, skipping review because a change seems simple is listed as a red flag. Critical issues must be fixed immediately and Important issues resolved before proceeding, regardless of perceived change size.