requesting-code-review

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

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/SESELOVSKYDarian/Vase --skill requesting-code-review-seselovskydarian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/SESELOVSKYDarian/Vase/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/SESELOVSKYDarian/Vase --skill requesting-code-review-seselovskydarian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent verification, letting bugs, architecture flaws, and unmet requirements slip into production. This Skill structures the review process by dispatching a dedicated code-reviewer subagent with precisely crafted context, catching issues before they cascade. ## Core Features & Use Cases - Structured Review Dispatch: Collects git SHAs and fills a reviewer template with implementation details, requirements, and commit range. - Severity-Categorized Feedback: The reviewer returns issues classified as Critical, Important, or Minor with file:line references and a merge readiness 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 completing a feature task, you capture the base and head commit SHAs, dispatch the reviewer with the plan reference, receive categorized feedback, fix Critical and Important issues, then proceed to the next task. ## Quick Start Ask the AI to request a code review of the changes you just implemented 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 commit SHAs with git rev-parse, then dispatch the code-reviewer subagent using the provided template. Fill in what was implemented, the plan or requirements, and the commit range so the reviewer evaluates the exact diff.

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 a git diff?

The reviewer checks code quality, architecture, testing, and requirement coverage against the plan. It also assesses production readiness including migration strategy, backward compatibility, and documentation completeness.

How are code review issues categorized by severity?

Issues are classified as Critical (bugs, security, data loss), Important (architecture problems, missing features, test gaps), or Minor (style, optimizations). Each issue includes a file:line reference, explanation, and suggested fix.

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.