requesting-code-review

Dispatch structured code-review tasks for git-based changes with severity categorization.

35|5|Updated Sep 20, 2025
One-click install
npx skills add https://github.com/zhanglongxiao111/indesign-cli --skill requesting-code-review-zhanglongxiao111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/zhanglongxiao111/indesign-cli/tree/main/.codex/skills/requesting-code-review
Command: npx skills add https://github.com/zhanglongxiao111/indesign-cli --skill requesting-code-review-zhanglongxiao111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code changes often ship with preventable issues because review happens too late; this Skill helps teams request a focused code review right after key work so defects are caught early.

Core Features & Use Cases

  • Trigger structured reviews at the right moments: enforces review after each subagent task, after major features, and before merge.
  • Send a well-scoped review payload: provides the reviewer with what was implemented, the plan/requirements, and an exact git range to evaluate.
  • Turn feedback into actionable fixes: guides how to address Critical/Important issues and how to respond if the reviewer is mistaken.

Quick Start

Ask the code-reviewer subagent to review your latest change by providing the implemented summary, plan/requirements, base SHA, head SHA, and a brief description.

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 structured code review for newly implemented git changes?

To request a structured code review, provide the reviewer with the implementation summary, plan/requirements, base SHA, head SHA, and a brief description of the changes. This dispatches a focused review task to validate the git diff range.

When should I trigger a pre-merge code review in a subagent workflow?

Trigger a pre-merge code review after each subagent task completes, after finishing major features, and before merging branches. This ensures timely quality validation so defects are caught early before they cascade.

What is the expected output of a pre-merge validation code review?

The expected output of a pre-merge validation code review is an explicit readiness verdict. The reviewer categorizes discovered issues by severity into Critical or Important levels to guide actionable fixes.

How do I handle feedback if the code reviewer identifies a Critical issue?

Address Critical and Important issues by applying actionable fixes based on the reviewer's feedback. If the reviewer is mistaken, the workflow provides guidance on how to respond with clarifications comparing implementation against requirements.

Do I need specific dependencies to run a git diff code review?

No external dependencies are required to run this git diff code review. You only need a git-based workflow environment to compare implementation against requirements and inspect the specified commit range.