requesting-code-review

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

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill requesting-code-review-shrek-abaper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/shrek-abaper/sap-nexus-agent/tree/main/.comet/skills/skills/requesting-code-review
Command: npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill requesting-code-review-shrek-abaper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code issues caught late compound into larger rework. This Skill dispatches a dedicated code reviewer subagent with precisely crafted context—git SHAs, requirements, and a structured review template—so completed work is verified against its plan before merging or moving to the next task. ## Core Features & Use Cases - Structured Review Dispatch: Fills a reusable reviewer prompt template with description, requirements, and base/head commit SHAs, then sends it to a general-purpose subagent. - Severity-Calibrated Feedback: The reviewer returns strengths, issues categorized as Critical/Important/Minor with file:line references, recommendations, and a merge-readiness verdict. - Read-Only Review Safety: The template forbids the reviewer from mutating the working tree, index, or HEAD, requiring git show/diff or a separate worktree for inspection. - Use Case: After finishing a task in subagent-driven development, capture BASE_SHA and HEAD_SHA, dispatch the reviewer, fix Critical and Important issues, then proceed to the next task 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 with a subagent?▼

Get 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, requirements, and the two SHAs. 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 useful when stuck, before refactoring, 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, and must use a separate temporary worktree if it needs to inspect another revision.

What should I do if the code reviewer is wrong?▼

Push back with technical reasoning and show code or tests that prove the implementation works. Fix Critical issues immediately and Important issues before proceeding, but valid feedback should not be argued against.

What output format does the code review produce?▼

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