requesting-code-review

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

1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/Fidasek009/agents --skill requesting-code-review-fidasek009
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Fidasek009/agents/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/Fidasek009/agents --skill requesting-code-review-fidasek009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When completing tasks or features, self-reviewing your own code burns context and misses issues. This Skill dispatches a dedicated code reviewer subagent with precisely crafted context so problems are caught before they cascade into more work. ## Core Features & Use Cases - Structured Reviewer Dispatch: Provides a ready-to-use prompt template (code-reviewer.md) that instructs a general-purpose subagent to review a git diff range against the plan or requirements. - Severity-Calibrated Feedback: The reviewer returns Strengths, Issues categorized as Critical/Important/Minor, Recommendations, and a clear merge-readiness verdict. - Read-Only Review Safety: The template enforces read-only inspection using git diff, git show, and git log, forbidding any mutation of the working tree or HEAD. - Use Case: After finishing a task in subagent-driven development, capture BASE_SHA and HEAD_SHA, 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 before merging?▼

Get the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template. Fill in the description, requirements, and SHA placeholders, and the reviewer returns categorized issues and a merge verdict.

How to review a git diff with an AI subagent?▼

Pass the subagent a base SHA and head SHA so it can run git diff --stat and git diff on that range. The template instructs it to check plan alignment, code quality, architecture, testing, and production readiness.

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.

Can the code reviewer subagent modify my working tree?▼

No. The template enforces a strictly read-only review using git show, git diff, and git log. If another revision is needed, the reviewer must use git worktree in a temporary directory and never move HEAD on the current checkout.

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 on the disputed point.