requesting-code-review

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

1|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/thienty1207/Hotel_Staff --skill requesting-code-review-thienty1207
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/thienty1207/Hotel_Staff/tree/main/.baron/core/skills/superpowers/requesting-code-review
Command: npx skills add https://github.com/thienty1207/Hotel_Staff --skill requesting-code-review-thienty1207

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed code changes often ship with undetected bugs, plan deviations, and quality gaps because self-review is unreliable and inline review burns the coordinator's context window. This Skill structures the review process by dispatching a dedicated reviewer subagent with precisely crafted context. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose reviewer subagent with a ready-made prompt template covering plan alignment, code quality, architecture, testing, and production readiness. - Severity-Calibrated Feedback: Returns findings categorized as Critical, Important, and Minor with file:line references, plus a clear merge verdict. - Read-Only Review Safety: Instructs the reviewer to never mutate the working tree, index, or HEAD, using git diff and git show for inspection. - Use Case: After finishing a feature task, capture the base and head commit SHAs, dispatch the reviewer with the template, fix Critical and Important issues, then proceed to the next task or merge. ## Quick Start Ask the AI to request a code review of the changes between the previous commit and HEAD using the code-reviewer template before merging.

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 with an AI subagent?

Capture the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer prompt template. Fill in the description, requirements, and SHA placeholders so the reviewer evaluates the exact diff range.

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, before refactoring as a baseline check, or after fixing a complex bug.

Can the reviewer subagent modify my working tree?

No. The template enforces a read-only review: the reviewer must not mutate the working tree, index, HEAD, or branch state. It inspects history with git show, git diff, and git log, using a separate git worktree only if another revision is needed.

What feedback format does the code review produce?

The reviewer returns Strengths, Issues categorized as Critical, Important, and Minor with file:line references, Recommendations, and an Assessment stating whether the work is ready to merge with brief technical reasoning.

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 disputed point before making changes.