dispatch-panel-review
Dispatch the four dimensional PR reviewers in parallel. Use when review_orchestrator starts or repeats a panel review, or when the user says dispatch panel review or /dispatch_panel_review. Do not review the diff yourself.
- License 许可
- MIT
- 所属仓库
- sazlin/loadout
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- dispatch-panel-review
- description
- Dispatch the four dimensional PR reviewers in parallel. Use when review_orchestrator starts or repeats a panel review, or when the user says dispatch panel review or /dispatch_panel_review. Do not review the diff yourself.
02 资源文件 2
- 参考文档evals/evals.json645 B
- 参考文档evals/files/brief.md60 B
03 SKILL.md 正文
Dispatch panel review
Launch review_correctness, review_maintainability, review_scale, and
review_security in one turn, in parallel, on the same GitHub PR / diff.
When to use
review_orchestratoris starting or repeating the Review phase- The user asks for
/dispatch_panel_reviewor a panel review
Do not use to fix code, judge VERIFIERS.md, or merge.
Steps
- Resolve the change set. Loop 1 is the full PR diff (
gh pr view/gh pr diffor the git range in the brief). Loop 2+ uses the two-dot resolver-commit range the orchestrator named (git diff <left-sha>..HEADforissue_resolvercommits since the previous panel), not the full PR vs base. Use that range as written. Do not recompute the left SHA. Every reviewer gets the same summary, paths, PR id, and range. - Issue four isolated subagent calls in a single response. One call per response is a protocol failure. Loops 2+ still dispatch all four reviewers. Never skip a reviewer.
- Each brief:
- "You are the
<agent>reviewer. Follow.claude/agents/<agent>.md." - "Return only your JSON issue schema. Do not edit files. Do not review other dimensions."
- Enough diff/path context that the reviewer does not need this chat.
- On loop 2+: "Review only that range. File regressions those resolver commits introduced."
- "You are the
- Wait for all four JSON reports. If a report is missing the issue schema,
one retry, then record that reviewer as
missing. - Do not review in-process. Do not write
TASKS_TO_RESOLVE.mdorTASKS_TO_RESOLVE-<short-sha>.mdhere (dedupe-and-write-tasksis next).
Harness
- Cursor: four
Taskcalls in one message (named agent type if available). Do not pass inherit or a Fast model; reviewers are pinned to Grok 4.6 medium, not Fast (grok-4.6[effort=medium,fast=false]). - Claude Code: four Agent calls using the custom agent names.
Guardrails
- Never become a single combined reviewer
- Never drop a reviewer's issues
- Never skip a reviewer on loop 2 or 3
- Never edit source,
VERIFIERS.md, or history in this skill
04 同仓库更多 Skills
demo
Demo skill
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback