requesting-code-review

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill requesting-code-review-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/requesting-code-review
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill requesting-code-review-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When completing tasks or features, self-reviewing your own changes is unreliable and consumes your working context. This Skill provides a structured process for dispatching an independent code reviewer subagent that evaluates a git diff against the original plan, catching Critical and Important issues before they cascade into more work. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose subagent with a precisely crafted prompt template (code-reviewer.md) containing the description, requirements, and git SHA range — never your session history. - Severity-Calibrated Feedback: The reviewer returns Strengths, Issues categorized as Critical/Important/Minor with file:line references, Recommendations, and a clear merge verdict. - Read-Only Review Guarantee: The template forbids the reviewer from mutating the working tree, index, or HEAD, and prohibits it from spawning its own subagents. - Use Case: After finishing Task 2 of a feature plan, you capture BASE_SHA and HEAD_SHA, dispatch the reviewer, receive feedback flagging a missing progress indicator as Important, fix it, and proceed to Task 3 with confidence. ## 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 a feature?

Capture the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template filled with a description, the requirements, and the SHA range. The reviewer returns categorized issues and a merge 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 as a baseline check, or after fixing a complex bug.

Can the code reviewer subagent modify my working tree?

No. The review is strictly read-only on the current checkout. The reviewer uses git show, git diff, and git log to inspect history, and must use a separate temporary worktree if it needs another revision checked out.

What should I do when the code reviewer reports issues?

Fix Critical issues immediately and Important issues before proceeding, while Minor issues can be noted for later. If you believe the reviewer is wrong, push back with technical reasoning and show code or tests that prove the implementation works.

Why dispatch a reviewer subagent instead of reviewing the diff myself?

Reviewing the diff inline burns the context window you need to coordinate the work. The subagent holds the diff and evaluation in its own context, returning only the findings, and receives precisely crafted context rather than your full session history.