address-issuelisted

# Address Issue Skill Fetches a GitHub issue, converts it into a tusk task, and immediately begins working on it using the full `/tusk` workflow. ## Step 1: Parse the Issue Reference Invoked with an optional issue number, full URL, or cluster selector: - `/address-issue 314` - `/address-issue https://github.com/gioe/tusk/issues/314` - `/address-issue --cluster worktree` (select one issue labeled `cluster:worktree`) - `/address-issue --cluster worktree --batch` - no argument to default to the newest open issue Parse flags first: - `--cluster <name>` sets `$CLUSTER`. Any `cluster:<name>` label currently present on the repo is accepted — the skill does not validate against a closed list, so new clusters added to GitHub work immediately without a skill edit. Run `gh label list --repo gioe/tusk --search "cluster:"` to see the current set if you're unsure which clusters exist. - `--batch` is valid only with `--cluster`. - A number or full URL must not be combined with `--cluster`; if both are present, stop and ask the user to choose one mode. Extract the issue number: - Full URL → parse the number from the path. - Number only → use it directly. - `--cluster <name>` without `--batch` → fetch open issues with that cluster label, then choose the highest-leverage issue: ```bash CLUSTER="<name>" gh issue list --repo gioe/tusk --state open --label "cluster:$CLUSTER" --limit 50 --json number,title,labels,updatedAt,url ``` Prefer the broadest canonical/root-cause issue in th