mkfixlisted

# Fixing Unified skill for fixing issues of any complexity with structured diagnosis. ## Process Flow (Authoritative) ``` Bug → Mode Select → Check Memory → Scout (MANDATORY) → Diagnose → [investigate → sequential-thinking → root cause?] → yes → Root-Cause Proof (6 fields, HARD GATE) → Complexity → Fix ROOT CAUSE → Verify+Prevent (MANDATORY) → pass → Finalize + Write to Memory → fail <3 → re-diagnose | fail 3+ → STOP ``` **This flow is authoritative.** If prose conflicts, follow the flow. **HARD GATE** Do NOT propose or implement fixes before completing Steps 1-2 (Scout + Diagnose). Symptom fixes are failure. Find the cause first through structured analysis, NEVER guessing. If 3+ fix attempts fail, STOP and question the architecture — discuss with user. Override: `--quick` allows fast scout→diagnose→fix for trivial issues (lint, type errors). ## Arguments - `--auto` — Autonomous mode (**default**). Auto-fixes blocking issues up to the cycle limit, then stops at *ready for user approval*. Never self-approves; score is advisory display only. - `--review` — Human-in-the-loop. Pause at each step. - `--quick` — Fast cycle for trivial bugs. - `--parallel` — Parallel `developer` agents per independent issue. - `--tdd` — Force regression test BEFORE the fix (writes the `.claude/session-state/tdd-mode` sentinel). Without `--tdd`, regression tests are recommended but not gated. Useful for security-sensitive fixes where you want to prove the bug first. ## Plan-First Gat