dx-swe-requesting-review

Dispatches a code-reviewer subagent to evaluate git diffs against requirements before merging.

3|5|Updated Jan 21, 2025
One-click install
npx skills add https://github.com/DEEPX-AI/dx_stream --skill dx-swe-requesting-review-deepx-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dx-swe-requesting-review
Source: https://github.com/DEEPX-AI/dx_stream/tree/main/.deepx/skills/dx-swe-requesting-review
Command: npx skills add https://github.com/DEEPX-AI/dx_stream --skill dx-swe-requesting-review-deepx-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without structured review, letting bugs and architectural issues compound across tasks. This Skill enforces early, frequent review by dispatching a dedicated code-reviewer subagent with precisely crafted context. ## Core Features & Use Cases - Structured Review Dispatch: Builds a reviewer prompt from a template with git SHAs, implementation summary, and requirements so the reviewer evaluates the work product, not session history. - Severity-Categorized Feedback: Returns issues classified as Critical, Important, or Minor with file:line references and a clear merge verdict. - Workflow Integration: Defines when to request review—after each task in subagent-driven development, after major features, and before merging to main. - Use Case: After completing a task that adds verification functions, you capture the base and head commit SHAs, dispatch the reviewer subagent, receive feedback flagging a missing progress indicator, fix it, and proceed to the next task. ## Quick Start Ask the agent to request a code review of the changes between the previous commit and HEAD using the dx-code-reviewer template before continuing.

Frequently Asked Questions about dx-swe-requesting-review

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

FAQPage Schema
How do I request a code review before merging changes?▼

Get the base and head commit SHAs with git rev-parse, then dispatch a code-reviewer subagent using the provided template. Fill in what was implemented, the requirements, and the commit range so the reviewer evaluates the actual diff.

When should code review be requested during development?▼

Review is mandatory 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.

How are code review issues categorized by severity?▼

Issues are classified as Critical (bugs, security risks, broken functionality), Important (architecture problems, missing features, test gaps), and Minor (style, optimizations). Each issue includes a file:line reference and an explanation of why it matters.

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 from the reviewer when the assessment seems inaccurate.

Why give the reviewer a fresh context instead of session history?▼

Providing only the git diff, requirements, and a description keeps the reviewer focused on the work product rather than your thought process. It also preserves your own context window for continued development work.