review-agent-orchestration

# Review Agents — Orchestration ## Overview Scans multi-agent projects (coordinator + specialists) for pub/sub topic naming conventions, loop safety (`max_iterations`), agent-registry wiring, port collisions in `dapr.yaml`, and cross-agent shared-state hazards. Read-only. Single-agent projects receive zero findings. ## Execution Order You MUST follow these phases in strict order. 1. **Resolve scope** — Read [`../shared/review-scope-prompt.md`](../shared/review-scope-prompt.md) and follow it to set `scope_root`. 2. **Detect target** — Read [`../shared/review-detect-target-agent.md`](../shared/review-detect-target-agent.md). If `topology == single-agent`, emit `No issues found.` and stop. 3. **Load checklist** — Based on `language`, read exactly one of: - `python` → [`../shared/review-agent-orchestration-python.md`](../shared/review-agent-orchestration-python.md) - `dotnet` → [`../shared/review-agent-orchestration-dotnet.md`](../shared/review-agent-orchestration-dotnet.md) 4. **Scan** — Apply every rule. Port-collision rules require parsing `dapr.yaml`; topic-routing rules require grepping for `publish_topic=` / `subscribe_topic=` / `DaprClient.PublishEventAsync(`. 5. **Report** — Format findings using [`../shared/review-report-format.md`](../shared/review-report-format.md). 6. **Show final message** — Emit the report from step 5 with a `## Next steps` block. ## Prerequisites - Read access to the project directory. ## Allowed tools `Read`, `Grep`, `Glob` only. #...