fix-pattern-cyclelisted

Wrap the six fix-pattern MCP tools behind a single intent-routed skill that enforces the Day 76 doctrine: every recurring bug class becomes a tracked pattern, every fix attempt carries an outcome, every validation cites a verifiable proof token. **Canonical source**: VantageRegistry (`get_skill_content name=fix-pattern-cycle`). The local `.claude/skills/fix-pattern-cycle/SKILL.md` in each workspace MUST be a byte-exact mirror of the VR canonical content. End of hand-copy — fetch from VR, do not edit locally. ## WORKFLOW **Step 1 — Parse intent** Map the user phrasing to one of six modes: - `create` — "create/new fix pattern", "log a fix pattern", "record this bug class" - `attempt` — "add fix attempt", "log attempt on pattern", "record fix try" - `validate` — "validate fix", "confirm pattern fix", "mark pattern validated" - `link` — "link issue to pattern", "attach issue #N to pattern" - `search` — "search fix patterns", "find pattern about X" - `list` — "list fix patterns", "show all patterns" If the phrasing is ambiguous, default to `list` and present the recent patterns so the user can pick. **Step 2 — Mode `create` (mcp__vantage-peers__create_fix_pattern)** Required inputs before the call: 1. `title` — short pattern name (≤80 chars), kebabable (e.g. "convex-cron-double-fire-on-deploy"). 2. `symptom` — one-paragraph description of the observable failure (logs, user-visible error, metric anomaly). 3. `rootCauseHypothesis` — one-paragraph mechanism. Mark `confirmed`