requesting-code-review

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

92|12|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/ARounder-183/HiFiShifter --skill requesting-code-review-arounder-183
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ARounder-183/HiFiShifter/tree/main/.github/skills/requesting-code-review
Command: npx skills add https://github.com/ARounder-183/HiFiShifter --skill requesting-code-review-arounder-183

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without systematic review, letting bugs, architecture problems, and unmet requirements slip into production. This Skill standardizes the review process by dispatching a dedicated code-reviewer subagent that compares your implementation against the original plan and categorizes issues by severity. ## Core Features & Use Cases - Structured Review Dispatch: Provides a repeatable workflow for gathering git SHAs and dispatching a code-reviewer subagent with a fill-in template. - Severity-Categorized Feedback: The reviewer template classifies findings as Critical, Important, or Minor, with file:line references and a clear merge verdict. - Workflow Integration: Defines when to request reviews—after each task in subagent-driven development, after major features, and before merging to main. - Use Case: After completing a feature task, you run the skill to get the base and head SHAs, dispatch the reviewer with your plan reference, receive categorized feedback, fix Critical and Important issues, and only then proceed to the next task. ## Quick Start Ask the AI to request a code review of your most recent commits against the task requirements before continuing to the next task.

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 an automated code review before merging?

Get the base and head git SHAs for your change range, then dispatch the code-reviewer subagent using the provided template with what was implemented, the plan reference, and the commit 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 useful when stuck on a problem or before refactoring to establish a baseline.

What does the code reviewer check in a git diff?

The reviewer checks code quality, architecture, testing coverage, and requirement compliance against the plan. It also assesses production readiness including migrations, backward compatibility, and documentation, then categorizes issues as Critical, Important, or Minor.

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

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 on the specific concern.

Can I skip code review for simple changes?

No, the skill explicitly warns against skipping review because a change seems simple. Critical issues must be fixed immediately and Important issues resolved before proceeding to subsequent work.