A GitHub issue-splitting workflow that turns one oversized issue into two to five smaller, linked sub-issues. It can optionally begin work on the first child issue.

Use it when an existing GitHub issue covers too much work for one change. It creates native parent-child links between the original issue and its smaller tasks.

Large issues are difficult to plan, review, and complete in one pull request. Splitting them makes the work easier to track while keeping the relationship to the original issue.

iflow-split — Skill by jepegit

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/jepegit/issue-flow/iflow-split

Any agent

npx skills add jepegit/issue-flow --skill iflow-split

Clone the repo

git clone --depth 1 https://github.com/jepegit/issue-flow

Made for: Claude Code, Codex, Cursor.

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

When invoked 1,947 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.

Model	Per session	Once invoked
Fable 5	$0.00029	$0.01947
Opus 5	$0.00015	$0.00974
Sonnet 5	$0.00006	$0.00389
Haiku 4.5	$0.00003	$0.00195

Measured yesterday against content hash 9012e72a0f19, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

iflow-split 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 yesterday.

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.

.cursor/skills/iflow-split/SKILL.md · 115 lines

How it starts

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

issue-flow — split an over-large issue (`/iflow-split`)

Follow this skill to cut one over-large GitHub issue into 2–5 flat child issues, link each as a GitHub native sub-issue of the parent, and optionally start the first child.

Do not use this skill from /iflow, /iflow-build, or /iflow-close. /iflow-split is explicit-only because it creates GitHub issues and parent/child links.

Coexists with:

/iflow-issue — creates one new issue. Use split when an existing issue is too big for one PR.
/iflow-epic — staged multi-issue work with Depends on and publish. If the cut needs stages or explicit deps, stop and point at /iflow-epic (create an anchor with /iflow-issue epic when missing). Do not create children here.

Input

<N> — parent issue number to split.
(nothing) — use the focus issue in .issueflows/01-current-issues/, else the issue-style branch ^\d+-.+. Ambiguous → ask.

Invoke: type iflow split in chat, or /iflow-split from the slash menu (iflow-split also works).

MODEL & EXECUTION DIRECTIVE

Profile: reasoning — Prioritize deep thinking and careful trade-offs over speed or token economy.

In Cursor: switch to a thinking-capable model before invoking this step (not Auto-only).

Keep scope tight to what this step requires.

Resolve project root (multi-root workspaces)

Before any git, gh, or .issueflows/ path operation in this workflow:

Resolution order (stop when unambiguous):

Explicit hints in slash input — root:<path>, repo:<folder-basename> (directory name, e.g. cellpy-core), or repo:owner/name.
CLI fast path — issue-flow agent resolve [-C <start>] [--from-file <active-file>] [--json]. Use the returned project_root and repo; pass -C <project_root> to other issue-flow agent … subcommands. When the answer came from the workspace registry, the payload sets resolved_via_workspace_default: true.
Branch context — exactly one workspace repo whose branch matches ^\d+- → that root.
Single scaffold — exactly one .issueflows/ tree visible in the workspace → that root.
Workspace default — an issueflow-workspace.toml at the workspace root (created with issue-flow workspace init) may name a default member repo; use it when no scaffold matched above. Tell the user the default was used.
Ambiguous → stop and ask; never guess between sibling repos.

Read the full file on GitHub · 115 lines

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.

yesterday First seen · 115 lines · 29 tokens per session scan A 9012e72a0f19

Subscribe to this mod's changes

iflow-split is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 19d ago), licensed MIT. It adds 29 tokens to every session and 1,947 once invoked, about $0.0001 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.

Productivity

systematic-debugging

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

obra/superpowers · 21 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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 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