- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add GanyuanRan/Aegis --skill requesting-code-review -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add GanyuanRan/Aegis --skill requesting-code-review -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add GanyuanRan/Aegis --skill requesting-code-review -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add GanyuanRan/Aegis --skill requesting-code-review -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/GanyuanRan/Aegis/tree/HEAD/skills/requesting-code-review來自發布者
Dispatch a reviewer subagent using the canonical code-reviewer.md template to
catch issues before they cascade. The reviewer gets precisely crafted context
for evaluation — never your session's history. This keeps the reviewer focused
on the work product, not your thought process, and preserves your own context
for continued work.
This skill is the canonical review-request workflow for method-pack implementation work. Use it to request review only after you have enough evidence, enough context, and a clear authority boundary for what the reviewer is being asked to assess.
Core principle: Review early, review often.
Findings First: Reviews lead with concrete findings before summary. Use bugs first, risk first, tests first. Strengths and general assessment are still useful, but they must not bury correctness, evidence, architecture, or retirement problems.
Review readiness is not merge approval. A review can reduce uncertainty and
recommend readiness, but it does not replace verification-before-completion
and does not grant completion authority.
Mandatory:
Optional but valuable:
Before you leave this workflow, you must be able to state:
Review in this method pack is advisory and evidence-oriented. It is not authoritative completion by itself.
Compare requirements and result in both directions: omissions or weakening, and unsupported additions or strengthening. Preserve relevant relationships, behavior, ownership and qualifiers within the authorized transformation. Pair an evidenced defect with a relevant valid case; do not add acceptance criteria, reject authorized summaries or corrections, or require exhaustive equivalence.
1. Gather minimum review inputs:
recording-architecture-decisions was used, or should be used, when
an ADR action or baseline sync closure is in scopeCONTEXT.md language when public/domain naming is in scope;
passive reading does not load active modelingIf you cannot answer these, stop and gather them before dispatching review.
2. Define the Git review scope:
# Before the coordinator's task commit
REVIEW_SCOPE=working-tree
BASE_SHA=$(git rev-parse HEAD)
# Or for already committed work
REVIEW_SCOPE=committed-range
BASE_SHA=<known-start>
HEAD_SHA=$(git rev-parse HEAD)
For working-tree review, identify task-owned untracked paths explicitly. Do not stage merely to make them visible to a reviewer.
3. Dispatch reviewer subagent:
Use the Task tool with a general-purpose reviewer subagent. Fill the canonical
template at requesting-code-review/code-reviewer.md; do not rely on a
separate named agent prompt.
Placeholders:
{WHAT_WAS_IMPLEMENTED} - What you just built{PLAN_OR_REQUIREMENTS} - What it should do{EVIDENCE} - Fresh tests, commands, logs, or verification already available{COMPATIBILITY_BOUNDARY} - What existing behavior or interfaces must not break{RETIREMENT_NOTES} - Old owner / fallback / patch / duplicate branch and expected disposition{REVIEW_SCOPE} - working-tree or committed-range{BASE_SHA} - Starting commit{HEAD_SHA} - Ending commit, or WORKTREE{DESCRIPTION} - Brief summary4. Act on feedback:
[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 reviewer subagent using requesting-code-review/code-reviewer.md]
WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
PLAN_OR_REQUIREMENTS: Task 2 from docs/aegis/plans/deployment-plan.md
EVIDENCE: pytest tests/index/test_verify.py -v -> 12 passed
COMPATIBILITY_BOUNDARY: Existing index format and CLI flags must remain stable
RETIREMENT_NOTES: Legacy repair fallback still exists in old helper; remove once new path covers all four issue types
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
[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]
Subagent-Driven Development:
Executing Plans:
Ad-Hoc Development:
The review request must prompt the reviewer to inspect at least:
scope: requirements | architecture | bothrecording-architecture-decisions handoff when ADR action or
baseline sync closure is in scopeestablishing-project-contextIf the review only asks “is this code good?”, it is underspecified.
Never:
If reviewer wrong:
See template at: requesting-code-review/code-reviewer.md
Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement unc
---name: requesting-code-reviewdescription: Use when requesting independent code review, after implementation slices, before merging high-risk work, or…---# skills/requesting-code-review/SKILL.md總覽
Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.
常見問題
從發布者下載 skills/requesting-code-review/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/GanyuanRan/Aegis。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。