skills.rest
whatswithavi
whatswithaviCOMMUNITY
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 28, 2026
Search Tags:#code quality#git#diff analysis#code review#subagent#pre-merge
One-click install
npx skills add https://github.com/whatswithavi/Ecchelon_project --skill requesting-code-review-whatswithavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/whatswithavi/Ecchelon_project/tree/main/.agent/skills/requesting-code-review
Command: npx skills add https://github.com/whatswithavi/Ecchelon_project --skill requesting-code-review-whatswithavi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent review, letting bugs, architecture flaws, and unmet requirements slip into production. This Skill structures the review request process so every task or feature gets evaluated by a dedicated reviewer subagent with precisely crafted context. ## Core Features & Use Cases - Structured Review Dispatch: Fills a code-reviewer template with implementation details, requirements, and git SHAs so the reviewer sees only the work product, not your session history. - Severity-Based Feedback: Returns issues categorized as Critical, Important, or Minor with file:line references and a clear merge readiness verdict. - Use Case: After completing a feature task, capture the base and head commit SHAs, dispatch the reviewer subagent with the plan reference, then fix Critical and Important issues before moving to the next task. ## Quick Start Ask the AI to request a code review of the changes between the current HEAD and the previous commit using the code-reviewer template.

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?▼

Get the base and head commit SHAs with git rev-parse, then dispatch the code-reviewer subagent using the template with what was implemented, the requirements, and the SHA range. The reviewer returns categorized issues and a merge readiness 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 check in a git diff?▼

The reviewer checks code quality, architecture, testing, and requirement coverage across the diff between the base and head SHAs. It also assesses production readiness including migrations, backward compatibility, and documentation.

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 on the reviewer's concern.

Why does the reviewer not see my session history?▼

The reviewer receives only the crafted template context, not your conversation history. This keeps the review focused on the work product itself and preserves your own context for continued work.

Related Skills

Explore More Software Engineering Skills→
posit-devposit-dev
4.2k

commit

Generates commit messages from git diffs matching the repository's existing commit conventions.

Official
Intermediate
WesleyMFrederickWesleyMFrederick

requesting-code-review

Dispatch a code-reviewer subagent to review Git changes between BASE_SHA and HEAD_SHA.

Community
Basic
phraphra

code-review

Review modified code files and auto-fix mechanical issues.

Community
Advanced
rolopez23rolopez23

simplify

Review staged code diffs and apply conservative refactors with human sign-off.

Community
Intermediate