Agent skill · Documentation

issue

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".

jeremylongshoregithub.com/jeremylongshoreGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill issue --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0.0
Allowed tools: ReadWriteEditBash(git:*)Bash(gh:*)GlobGrepAgentSkillAskUserQuestion
Requires: Claude Code, Codex, OpenCode, Antigravity (needs gh CLI + git remote); Desktop/web via pasted issue text (lossy)
Path: plugins/ai-agency/hyperflow/skills/issue/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,596
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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

More from claude-code-plugins-plus-skills
All skills →
orchestrating-multi-agent-systemsExecute orchestrate multi-agent systems with handoffs, routing, and workflows across AI providers.…Workflow & Productivitypodium-review-request-automationTrigger Podium review requests from Shopify order-shipped events and survive the delivery-side…Code Review & Qualitypodium-contact-dedupDeduplicate Podium contacts in production and survive the data-quality failures — phone-format…Data & Analyticsvalidating-ai-ethics-and-fairnessValidate AI/ML models and datasets for bias, fairness, and ethical concerns. Use when auditing AI…AI & Agentsdatabricks-cost-leak-hunterHunt down Databricks cost leaks — wasted DBUs, idle clusters, oversized SQL warehouses, and…Databasesbuilding-automl-pipelinesBuild automated machine learning pipelines with feature engineering, model selection, and…Data & Analytics
About this skill
What does the issue skill do?

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".

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill issue --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.