Issue
Use when starting a chain from a GitHub issue, turning an issue URL or number into a...
Install
npx skills add jeremylongshore/tons-of-skills-marketplace --skill issue -g -a claude-code -y- Repository
- jeremylongshore/tons-of-skills-marketplace2.9k
- Category
- Git and review
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,506 tokens
- Runs scripts
- No, instructions only
What it does
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".
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'sorigin. No GitHub remote → stop withNo 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 exactgh auth login+gh pr createcommands to finish by hand. Never half-post.gh issue view <n> --json title,body,comments,labels,author,state,url. Closed issue → confirm intent viaAskUserQuestion(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. |
