​

/fix — Fix-Review Loop

​

When to Use

• /review returned a FIX-FIRST verdict with CRITICAL or HIGH gaps
• Orchestrator hands off unresolved gaps after execution review

​

Flow

1. Parse gaps — extract gap list from FIX-FIRST verdict (severity, files, failing checks).
2. Dispatch fixer — send gaps + original wish criteria to fix subagent.
3. Re-review — dispatch review subagent to validate the fix.
4. Evaluate verdict:

5. Escalate (if needed) — mark task BLOCKED, report remaining gaps.

​

Escalation Format

Fix loop exceeded (2/2). Escalating to human.
Remaining gaps:
- [CRITICAL] <gap description> — <file>
- [HIGH] <gap description> — <file>

​

Dispatch

# Spawn a fixer subagent
genie spawn fixer

# Spawn a reviewer subagent (separate from fixer)
genie spawn reviewer

​

Task Lifecycle Integration

​

Rules

• Never fix and review in the same session — always separate subagents
• Never exceed 2 fix loops — escalate, don’t spin
• Include original wish criteria in every fix dispatch
• If identical gaps persist across loops, escalate immediately