A workflow that takes a GitHub issue—a tracked software task—and guides it through code review, planning, implementation, pull-request creation, and cleanup.

Use it to implement a specific GitHub issue end to end, including creating a pull request for review.

It keeps issue-based development organised from the original request through proposed code changes.

issue-flow — Skill for Claude Code by notedit/happy-skills

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add notedit/happy-skills --skill issue-flow

Clone the repo

git clone --depth 1 https://github.com/notedit/happy-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/notedit/happy-skills/issue-flow/github.svg)](https://agentmods.dev/skills/notedit/happy-skills/issue-flow)

Your own site

<a href="https://agentmods.dev/skills/notedit/happy-skills/issue-flow"><img src="https://agentmods.dev/badge/skills/notedit/happy-skills/issue-flow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/notedit/happy-skills/issue-flow"><img src="https://agentmods.dev/badge/skills/notedit/happy-skills/issue-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,293 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00074	$0.02293
Opus 5.5	$0.00030	$0.00917
Sonnet 5.5	$0.00015	$0.00459
Haiku 4.5	$0.00007	$0.00229

Measured 1mo ago against content hash 8f1f645aa143, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

issue-flow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/dev/issue-flow/SKILL.md · 268 lines

How it starts

The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Issue Flow — AI-Native Issue-Driven Development

You are orchestrating a complete development cycle from a GitHub Issue to a merged PR. Follow the phases below strictly. Every major decision requires human confirmation.

Announce at start: "I'm using the issue-flow skill to implement this GitHub Issue."

Initial request: $ARGUMENTS

Phase 0: Preflight

Goal: Validate environment and resolve the target Issue.

Actions:

Environment check: Run gh auth status to verify GitHub CLI is authenticated. If it fails, tell the user to run gh auth login and stop.
Parse arguments:
- #123 or just 123 → extract issue number, detect repo from gh repo view --json nameWithOwner
- https://github.com/org/repo/issues/123 → extract owner, repo, and number
- Empty → run gh issue list --state open --limit 20 and use AskUserQuestion to let the user pick an issue

Fetch Issue details:

gh issue view <N> --json number,title,body,labels,comments,assignees,state

Store: ISSUE_NUMBER, ISSUE_TITLE, ISSUE_BODY, ISSUE_LABELS.

Check for existing work:
- Search for branch issue/<N>-* via git branch -a --list '*issue/<N>*'
- If found, AskUserQuestion: resume existing branch / start fresh / cancel
Detect project features (used later for team composition):
- Has test framework? (check for jest.config*, vitest.config*, pytest.ini, *test* dirs)
- Has CI? (check .github/workflows/, .gitlab-ci.yml, etc.)
- Has linter? (check .eslintrc*, biome.json, .prettierrc*)
- Primary language(s) from file extensions

Phase 1: Worktree Setup

Goal: Create an isolated workspace.

Actions:

Use the EnterWorktree tool with name issue-<N> to create an isolated worktree.
Create and switch to branch issue/<N>-<slugified-title>:
- Slugify: lowercase, replace spaces/special chars with -, truncate to 50 chars
- Example: Issue #42 "Add OAuth2 Login Support" → issue/42-add-oauth2-login-support
- Run: git checkout -b issue/<N>-<slug>

Read the full file on GitHub · 268 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 268 lines · 74 tokens per session scan A 8f1f645aa143

Subscribe to this mod's changes

issue-flow is a skill published in the GitHub repository notedit/happy-skills (339 stars, last pushed 7mo ago), licensed MIT. It adds 74 tokens to every session and 2,293 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow Project management

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens

cuga-github-issues

Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…

cuga-project/cuga-agent · 88 tokens