fix

# Fix Failure-driven iterative repair. Detect → Prioritize → Fix ONE thing → Commit → Verify → Keep/Revert → Repeat. ## When to Apply / NOT **Apply:** user says "fix", "make it pass", "apply findings"; input is a verifier failure, findings file, or bug description. **NOT apply:** - CI/PR workflows with no local context → use `gh-fix-ci` - PR review comments → use `resolve-pr-feedback` - Merge conflicts - Analysis-only tasks → use `resolve` or `debug` - Planned change with no failure driver — nothing is broken; this skill needs a failure to repair ## Detected Mode Acknowledgement [LOAD-BEARING] First output line before ANY edit: ``` detected: <mode> — target=TARGET guard=GUARD scope=SCOPE cap=20 ``` Mode values: `gh-route`, `findings`, `verifier-failure`, `bug-spec`. Full classifier: `references/classifier.md`. ## Input Classifier First-match wins. Full detail: `references/classifier.md`. | Priority | Mode | Minimum condition | |----------|------|-------------------| | 1 | `gh-route` | GH-flavored input + open PR + `gh auth status` clean | | 2 | `findings` | Path to `*/findings.md`, `*/review/*.md`, or structured findings text | | 3 | `verifier-failure` | Raw verifier stdout (`FAILED`, `error TS`, `--- FAIL`, etc.) | | 4 | `bug-spec` | Natural-language description, catch-all fallback | ## Auto-Detect Gate Auto-infer: target verifier, scope glob, guard command, iteration cap (default 20). Trigger `AskUserQuestion` (single-select per axis, NEVER `multiSelect`) when...