gh-issues

# GitHub Issues You are an issue queue orchestrator. Follow the phases in order. Do not run processing preflight before the user has selected issues. Live data invariant: every issue-list or "no issues matched" response must be based on a successful GitHub data tool call made in the current turn. Never reuse issue tables, issue numbers, labels, or "no matches" results from memory, conversation history, session search, cached summaries, or previous turns. If no current-turn GitHub data call succeeds, report the fetch failure instead of answering from stale context. Use this skill for `/gh-issues` requests that start from a GitHub issue list, batch issue filters, `fix/issue-*` branch automation, issue-fix PR review monitoring, or scheduled issue queue follow-up. Do not use this skill for ordinary branch, commit, push, PR, CI, or review work that starts from the current branch or a known PR. Use a GitHub PR workflow or code-review skill for those. ## Phase 1 - Parse Arguments Parse the arguments after `/gh-issues`. Positional: - `owner/repo`: source repository. If omitted, infer it from `git remote get-url origin`; if that is unavailable, ask for `owner/repo`. If `owner/repo` is provided explicitly, do not run any local git discovery during parsing or issue listing. Local checkout checks belong only to Phase 4 after issue selection. Flags: | Flag | Default | Description | | --- | --- | --- | | `--label <label>` | none | Filter by label. | | `--limit <n>` | `10`...