requesting-code-review

name	requesting-code-review
description	Use when completing tasks, implementing major features, or before 合併 to verify work meets requirements
trigger	when_needed
language	zh-TW
adapted_from	openskills/requesting-code-review
version	1.0.0-antigravity
original_license	Unknown

REQUESTING-CODE-REVIEW 處理指南

技能版本: v1.0 (Antigravity 適配版)
原始來源: openskills/requesting-code-review
語言: 繁體中文

概述

Use when completing tasks, implementing major features, or before 合併 to verify work meets requirements

---

Requesting Code Review

Dispatch superpowers:code-reviewer subagent to catch issues before they cascade.

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)

詳細內容請參閱：[example_2.txt](examples/example_2.txt)

[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 superpowers:code-reviewer subagent]
  WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
  PLAN_OR_REQUIREMENTS: Task 2 from docs/plans/deployment-plan.md
  BASE_SHA: a7981ec
  HEAD_SHA: 3df7661
  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types

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

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

Integration with Workflows

Subagent-Driven Development:

• Review after EACH task
• Catch issues before they compound
• Fix before moving to next task

Executing Plans:

• Review after each batch (3 tasks)
• Get feedback, apply, continue

Ad-Hoc Development:

• Review before merge
• Review when stuck

Red Flags

Never:

• Skip review because "it's simple"
• Ignore Critical issues
• Proceed with unfixed Important issues
• Argue with valid technical feedback

If reviewer wrong:

• Push back with technical reasoning
• Show code/tests that prove it works
• Request clarification

See template at: requesting-code-review/code-reviewer.md

---

專案整合

此技能已適配 Antigravity 系統：

• 遵循 skills/_base/coding_style.md 編碼規範
• 與 skills/_base/architecture.md 架構模式一致
• 符合 Constitution v3.1 語言規範 (繁體中文)

相關技能

可搭配以下技能使用：

• systematic-debugging - 系統化除錯
• verification-before-completion - 完成前驗證