skills.rest
erwinv2k-TKG
erwinv2k-TKGCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

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

Updated Mar 26, 2026
Search Tags:#code quality#git#code review#development workflow#subagent#severity triage#merge verification
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill requesting-code-review-erwinv2k-tkg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill requesting-code-review-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It catches bugs, architecture flaws, and requirement gaps early by routing completed work through an independent code review before issues compound or reach the main branch. ## Core Features & Use Cases - Structured Review Dispatch: Fills a code-reviewer template with what was implemented, the plan, and git SHAs so the reviewer gets precise context instead of session history. - Severity-Based Feedback: Returns issues categorized as Critical, Important, or Minor with file:line references and a clear merge verdict. - Workflow Integration: Supports subagent-driven development (review after each task), plan execution (review per batch), and ad-hoc reviews before merging. - Use Case: After finishing a feature task, you capture the base and head commit SHAs, dispatch the reviewer subagent, fix the Important issues it flags, and only then 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 code-reviewer template before continuing.

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

Get the base and head commit SHAs with git rev-parse, then dispatch the code-reviewer subagent with what was implemented, the plan or requirements, and both SHAs. The reviewer returns categorized issues and a merge readiness verdict.

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 grouped as Critical (bugs, security, data loss), Important (architecture problems, missing features, test gaps), and Minor (style, optimizations). Each issue includes a file:line reference, why it matters, and how to fix it.

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

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

Why does the reviewer not receive my session history?▼

The reviewer gets only the crafted template context—implementation summary, requirements, and git range—so it evaluates the work product itself rather than your thought process, while preserving your own context for continued work.

Related Skills

Explore More Software Engineering Skills→
HillBombCreationsHillBombCreations

cmd-bug-review

Compare commits against research and plan documents using a 12-point checklist.

Official
Intermediate
gquthiergquthier
14

requesting-code-review

Dispatch a reviewer subagent to validate code changes before merging.

Community
Advanced
DataDogDataDog
648

lint

Run Hatch-based lint, format, and quality checks on modified files.

Official
Advanced
basicmachines-cobasicmachines-co
4.0k

fix-pr-issues

Resolves pull request feedback and failed checks, then re-runs the Codex review gate.

Official
Intermediate