| 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 <url>", "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 (/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 (review an incoming PR).
Step 0 — Preflight
- 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.
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.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 over the full
thread (body + comments + labels). Classify:
| 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. |
Already-solved check (mandatory): before planning any work, the triage agent verifies against current
whether the ask is already satisfied — issues are often filed against stale versions. Partially-satisfied →
the spec scopes only the remaining delta and says so.
