Agent Skills › xintaofei/codeg › requesting-code-review

requesting-code-review

GitHub

用于在开发任务完成、重大功能实现或合并前，调度代码审查子代理以提前发现潜在问题。通过提供精确上下文而非会话历史，确保审查质量，并根据反馈修复关键和重要缺陷，保障代码质量。

src-tauri/experts/skills/requesting-code-review/SKILL.md xintaofei/codeg

Trigger Scenarios

完成子代理驱动的开发任务后实现重大功能后合并到主分支前陷入困境需要新视角时

Install

npx skills add xintaofei/codeg --skill requesting-code-review -g -y

More Options

Non-standard path

npx skills add https://github.com/xintaofei/codeg/tree/main/src-tauri/experts/skills/requesting-code-review -g -y

Use without installing

npx skills use xintaofei/codeg@requesting-code-review

指定 Agent (Claude Code)

npx skills add xintaofei/codeg --skill requesting-code-review -a claude-code -g -y

安装 repo 全部 skill

npx skills add xintaofei/codeg --all -g -y

预览 repo 内 skill

npx skills add xintaofei/codeg --list

SKILL.md

Frontmatter

{
    "name": "requesting-code-review",
    "description": "Use when completing tasks, implementing major features, or before merging to verify work meets requirements"
}

Requesting Code Review

Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history.

Core principle: Review early, review often.

When to Request Review

Mandatory:

After each task in subagent-driven development
After completing major feature
Before merge to main

Optional but valuable:

When stuck (fresh perspective)
Before refactoring (baseline check)
After fixing complex bug

How to Request

1. Get git SHAs:

BASE_SHA=$(git rev-parse HEAD~1)  # or origin/main
HEAD_SHA=$(git rev-parse HEAD)

2. Dispatch code reviewer subagent:

Dispatch a general-purpose subagent, filling the template at code-reviewer.md

Placeholders:

{DESCRIPTION} - Brief summary of what you built
{PLAN_OR_REQUIREMENTS} - What it should do
{BASE_SHA} - Starting commit
{HEAD_SHA} - Ending commit

3. Act on feedback:

Fix Critical issues immediately
Fix Important issues before proceeding
Note Minor issues for later
Push back if reviewer is wrong (with reasoning)

Example

[Just completed Task 2: Add verification function]

You: Let me request code review before proceeding.

BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)

[Dispatch code reviewer subagent]
  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
  PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
  BASE_SHA: a7981ec
  HEAD_SHA: 3df7661

[Subagent returns]:
  Strengths: Clean architecture, real tests
  Issues:
    Important: Missing progress indicators
    Minor: Magic number (100) for reporting interval
  Assessment: Ready to proceed

You: [Fix progress indicators]
[Continue to Task 3]

Common Rationalizations

Excuse	Reality
"I'll just review the diff myself instead of dispatching a reviewer"	You're the coordinator — reviewing the diff inline burns the context window you need to keep driving the work. Dispatch a reviewer subagent: the diff and the evaluation live in its context, and only the findings come back to you.
"The reviewer needs my whole session history to understand the change"	Hand it precisely crafted context, never your session's history. That keeps the reviewer on the work product, not your thought process.