requesting-code-review

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

2|Updated May 30, 2026
One-click install
npx skills add https://github.com/virahitvin8/crafty-gis --skill requesting-code-review-virahitvin8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/virahitvin8/crafty-gis/tree/main/GIT_STAR/assignment-generator/antigravity-skills-main/antigravity-skills-main/skills/requesting-code-review
Command: npx skills add https://github.com/virahitvin8/crafty-gis --skill requesting-code-review-virahitvin8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent verification, letting bugs, plan deviations, and quality issues cascade into later work. This Skill structures the process of requesting an unbiased code review from a fresh subagent that sees only the work product, not your session history. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose reviewer subagent with a precisely crafted prompt containing the description, requirements, and git SHA range. - Structured Review Template: The code-reviewer.md template enforces severity-calibrated feedback (Critical, Important, Minor) with file:line references and a clear merge verdict. - Workflow Integration: Defines mandatory review checkpoints after each task in subagent-driven development, after major features, and before merging to main. - Use Case: After completing a task that adds index verification functions, you capture the base and head SHAs, dispatch the reviewer with the plan reference, receive categorized issues, fix the Important ones, and proceed to the next task with confidence. ## Quick Start Ask the AI to request a code review of your latest commits using the code-reviewer template before merging to main.

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 to main?

Capture 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 major features, and before merging to main. It is also valuable when stuck, before refactoring for a baseline check, 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. It examines the git diff between the provided SHAs and reports strengths, issues by severity, recommendations, and a merge readiness assessment.

Why use a separate subagent for code review instead of self-review?

A separate subagent receives only the crafted context and git diff, never your session history, keeping it focused on the work product rather than your reasoning. This provides a fresh, unbiased perspective while preserving your own context for continued work.

What should I do if I disagree with the code review feedback?

Push back with technical reasoning and show code or tests that prove the implementation works. Fix Critical issues immediately and Important issues before proceeding, but valid disagreement with evidence is encouraged over blind acceptance.