requesting-code-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often ship with undetected bugs, plan deviations, or quality gaps because self-review misses issues. This Skill dispatches an independent code reviewer subagent with precisely crafted context to catch Critical and Important issues before they cascade into more work. ## Core Features & Use Cases - Structured Review Dispatch: Builds a reviewer prompt from a template with description, requirements, and git SHA range placeholders. - Severity-Calibrated Feedback: Returns findings categorized as Critical, Important, and Minor with file:line references and a merge verdict. - Workflow Integration: Fits subagent-driven development, plan execution, and ad-hoc development with review checkpoints after each task or before merge. - Use Case: After completing a feature task, capture BASE_SHA and HEAD_SHA, dispatch the reviewer subagent with the plan reference, then fix flagged issues before starting the next task. ## Quick Start Ask the AI to request a code review of the changes between the previous commit and HEAD using the code-reviewer template before merging.

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 for my changes before merging?▼

Get the base and head git SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template filled with your change description, requirements, and SHA range. The reviewer returns categorized issues and a merge 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 subagent check?▼

The reviewer checks plan alignment, code quality, architecture, testing, and production readiness using the git diff between the provided SHAs. It reports strengths, issues by severity with file:line references, recommendations, and a merge readiness assessment.

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

Push back with technical reasoning and show code or tests that prove the implementation works. You can also request clarification, but never ignore valid Critical or Important issues without justification.

Why does the reviewer not receive my session history?▼

The reviewer gets only precisely crafted context—description, requirements, and git range—so it evaluates the work product rather than your thought process. This also preserves your own context window for continued work.