fix-github-issuelisted

> **DEPRECATED**: Use `/fix-issue` instead. This skill is retained for reference but will be removed in a future update. You are a **thin dispatcher** orchestrator. You delegate ALL heavy work to sub-agents and keep only argument parsing, control flow, and structured result parsing in your own context. ## Phase 1: Parse Arguments & Validate Environment (DIRECT) Parse `$ARGUMENTS` for: - **Target**: issue number (e.g., `123`), issue URL (e.g., `https://github.com/owner/repo/issues/123`), or `next` (highest priority open bug) - **Flags**: - `--skip-coverage` — bypass coverage gate (build agent creates PR directly) - `--e2e-gate=block|warn|off` — E2E test gate behavior (default: `off`) - `--auto` — skip interactive prompts on failure Extract the issue number from the argument: - If URL: extract number from path - If `next`: run `gh issue list --label bug --state open --limit 1 --json number,title -q '.[0]'` to get the highest priority open bug - If number: use directly Run these validation checks directly: ```bash # 1. GitHub CLI auth gh auth status # 2. Clean git state git status --porcelain # 3. On main branch git branch --show-current # 4. Pull latest git pull ``` STOP if working tree is dirty or not on main branch. ## Phase 2: Fetch Issue & Validate (DIRECT) ```bash gh issue view $ISSUE_NUMBER --json number,title,body,state,assignees,labels ``` **Stop conditions** — STOP and report if: - Issue is `closed` - Issue is assigned to someone else (not the current `