fix-issue

# Fix Issue Systematic issue resolution with hypothesis-based root cause analysis, similar issue detection, and prevention recommendations. ## Quick Start ```bash /ork:fix-issue 123 /ork:fix-issue 456 ``` > **Opus 5**: Root cause analysis uses native adaptive thinking. Dynamic token budgets scale with context window for thorough investigation. > **CC ≥ 2.1.119 multi-host note (M122):** Issue fetching works against GitHub, GitLab, Bitbucket, and GitHub Enterprise. The argument is either a numeric ID (use the configured default remote's host) or a full URL (parsed via `parsePrUrl`/`parseIssueUrl` from `src/hooks/src/lib/pr-host-parser.ts`). Branch on the detected host family for the right CLI: `gh issue view` (GitHub/GHE), `glab issue view` (GitLab), `bb issue view` (Bitbucket). Reference: `src/skills/chain-patterns/references/pr-from-platform.md`. ## Argument Resolution ```python ISSUE_NUMBER = "$ARGUMENTS[0]" # e.g., "123" (CC 2.1.59 indexed access) # $ARGUMENTS contains the full argument string # $ARGUMENTS[0] is the first space-separated token ``` ## STEP -1: MCP Probe + Resume Check **Run BEFORE any other step.** Detect available MCP servers and check for resumable state. ```python # Probe MCPs (parallel — all in ONE message): # memory is alwaysLoad in .mcp.json (CC 2.1.121+, #1541) — probe below kept as fallback for older CC: ToolSearch(query="select:mcp__memory__search_nodes") ToolSearch(query="select:mcp__context7__resolve-library-id") # Write capability map...