issue-flow

issue-flow is a skill for Claude Code, Codex from notedit/happy-skills. It costs 74 tokens per session (2,293 once invoked), scanned A, original, MIT.

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

In plain words
What is it for?
Use it to implement a specific GitHub issue end to end, including creating a pull request for review.
Why use it?
It keeps issue-based development organised from the original request through proposed code changes.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/notedit/happy-skills/issue-flow
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, Codex.

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.

agentmods badge for issue-flow

README.md
[![agentmods](https://agentmods.dev/badge/skills/notedit/happy-skills/issue-flow.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.svg" alt="Measured on agentmods" 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. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00074 $0.02293
Opus 5 $0.00037 $0.01146
Sonnet 5 $0.00015 $0.00459
Haiku 4.5 $0.00007 $0.00229

Measured 4d ago against content hash 8f1f645aa143, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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:

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

  2. 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
  3. Fetch Issue details:

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

    Store: ISSUE_NUMBER, ISSUE_TITLE, ISSUE_BODY, ISSUE_LABELS.

  4. 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
  5. 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:

  1. Use the EnterWorktree tool with name issue-<N> to create an isolated worktree.
  2. 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.

  1. 4d 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 (340 stars, last pushed 6mo ago), licensed MIT. It adds 74 tokens to every session and 2,293 once invoked, about $0.0004 per session on Opus 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens