issue

# Issue GitHub-native **entry point** for the chain: one issue URL in, one reviewed pull request out. This skill owns ingestion, triage, and spec synthesis; everything after that is the standard chain (`/hyperflow:plan` → `/hyperflow:dispatch`) with GitHub chain args propagated so dispatch's Step 5 offers the **PR exit**. The maintainer-side counterpart is [`/hyperflow:pr`](../pr/SKILL.md) (review an incoming PR). ## Step 0 — Preflight 1. Resolve the argument: full URL, `#N`, or bare number against the current repo's `origin`. No GitHub remote → stop with `No GitHub remote — /hyperflow:issue needs a repo with an origin on GitHub.` 2. `gh auth status` (once per chain). Unauthenticated → continue in **local-only mode**: the chain still runs, the PR exit and any comment posting are skipped, and the wrap-up prints the exact `gh auth login` + `gh pr create` commands to finish by hand. Never half-post. 3. `gh issue view <n> --json title,body,comments,labels,author,state,url`. Closed issue → confirm intent via `AskUserQuestion` (`Work on it anyway / Stop` — binary, no marker). ## Step 1 — Triage (decision agent) Dispatch a triage consultation per [`../hyperflow/task-triage.md`](../hyperflow/task-triage.md) over the full thread (body + comments + labels). Classify: | Class | Route | |---|---| | Bug report | Root-cause discipline from [`../trace/SKILL.md`](../trace/SKILL.md) — reproduce before any patch; then the fix chain on `fix/issue-<n>-<slug>` | | Feature / enha...