name: issue description: | Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the standard chain with a PR exit. Trigger with /hyperflow:issue, "work on issue #N", "fix this issue ", "implement this issue", "triage issue #N and raise a PR". allowed-tools: Read, Write, Edit, Bash(git:), Bash(gh:), Glob, Grep, Agent, Skill, AskUserQuestion argument-hint: "<issue url | #number> [pr=auto|ask|never] [comment=ask|never]" version: 1.0.0 license: MIT compatibility: Claude Code, Codex, OpenCode, Antigravity (needs gh CLI + git remote); Desktop/web via pasted issue text (lossy) tags: [github, issue, triage, chain-starter, pull-request, multi-agent]

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 ( → ) with GitHub chain args propagated so dispatch's Step 5 offers the . The maintainer-side counterpart is (review an incoming PR).

Class	Route
Bug report	Root-cause discipline from `../trace/SKILL.md` — reproduce before any patch; then the fix chain on `fix/issue-<n>-<slug>`
Feature / enhancement	`/hyperflow:plan` chain on `feat/issue-<n>-<slug>`
Question / discussion	Draft a reply, show it, and offer to post (gated by `comment=`). Never a code chain.
Invalid / spam / already fixed	Report the finding + draft a closing reply (gated). Stop.

Failure	Behavior
`gh` missing or unauthenticated	Local-only mode (Step 0.2) — chain runs, outbound steps print manual commands
Issue not found / no access	Stop: `Issue #<n> not found in <repo> — check the number and gh auth scope.`
Rate-limited	Back off once, then continue local-only with a warning
Triage says already fixed	Report with evidence (commit/version); draft closing reply; no chain
Headless (no interactive channel)	Requires `pr=` + `comment=` pre-elected; otherwise stop before Step 3 with explicit reason

issue

Install

Related skills

Questions

Issue

Step 0 — Preflight

Step 1 — Triage (decision agent)

Step 2 — Spec synthesis

Step 3 — Clarify

Step 4 — Chain

Step 5 — PR exit (owned by dispatch)

Iron rules

Error handling

Portability

Doctrine