メニュー
Spawn superpowers:code-reviewer on an item with a self-contained briefing. Includes premise-validation latitude and working-tree hygiene clauses.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Every "tests pass" / "build green" / "feature works" claim needs the actual command output pasted into the conversation. Bare assertions are worth zero.
The operating loop every session follows — register, tick, pick, work, checkpoint, test, review, commit, close. Use whenever you start or resume work on a squad-managed repo.
Post often, post small, post honestly. The team needs visibility into your non-obvious state — not a change log. Use the typed verbs (thinking / milestone / stuck / fyi / ask) so peers can route attention.
Tick the squad team — surface mentions and file conflicts. Address mentions BEFORE continuing other work.
Before signing off — whether you finished an item or stopped mid-flight — post a 3-bullet summary. Shipped, in flight / queued, surprised by. Three bullets, no ceremony.
Run a structured intake interview with the user — open a session, ask one focused question per turn, draft the bundle, confirm with the user, then commit. Supports green-field (mode=new) and refine-mode (mode=refine) flows.
| name | squad-review |
| description | Spawn superpowers:code-reviewer on an item with a self-contained briefing. Includes premise-validation latitude and working-tree hygiene clauses. |
| argument-hint | <ITEM-ID> |
| allowed-tools | ["Bash","Read","Task"] |
| paths | [".squad/items/**"] |
| disable-model-invocation | true |
You are requesting code review for item $ARGS. Invoke the squad-code-review-mandatory skill to construct the briefing correctly, then read superpowers:requesting-code-review to brief the reviewer.
First, post the request to the item thread:
squad review-request $ARGS
Then spawn the reviewer with a self-contained briefing. The reviewer does not see this conversation; the prompt must include:
.squad/items/$ARGS-*.md — the ## Acceptance criteria is the contract.git diff main...HEAD inline if small, otherwise give the command..bak files, scratch test files, or uncommitted edits behind."When the reviewer returns, use superpowers:receiving-code-review to evaluate each finding. Do not perform-agree. Verify each one, push back on the wrong ones with evidence, file out-of-scope findings as fresh items.