New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Iflow Split

by jepegit in jepegit/cellpy

Split one over-large GitHub issue into linked child issues (native sub-issues), then optionally start the first child.

MITAuto-check passed

Install Iflow Split

skills CLI
$ npx skills add jepegit/cellpy --skill iflow-split -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jepegit/cellpy iflow-split --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jepegit/cellpy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/iflow-split .claude/skills/iflow-split && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
iflow-split
GitHub stars
110
Token cost
~1.8k tokens
SKILL.md length
930 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Split one over-large GitHub issue into linked child issues (native sub-issues), then optionally start the first child.

  • Works in 3 steps: draft children → create and link → optional handoff
  • SKILL.md covers Input, Instructions and Constraints
  • Calls gh and git

What it does

Iflow Split is an agent skill from jepegit/cellpy. Split one over-large GitHub issue into linked child issues (native sub-issues), then optionally start the first child.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with GitHub. The repository describes itself as: extract and tweak data from electrochemical tests of cells. The licence is MIT.

Example prompts

  • “/iflow-split”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. draft children
  2. create and link
  3. optional handoff

What it can do on your machine

Read from SKILL.md and the folder at commit ff2c665. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Iflow Split loads about 1.8k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 930 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jepegit/cellpy at commit ff2c665, republished under its MIT licence (© jepegit). 930 words, ~1,813 tokens.

Download SKILL.mdSave it as .claude/skills/iflow-split/SKILL.md (or your agent's skills folder).
name
iflow-split
description
Split one over-large GitHub issue into linked child issues (native sub-issues), then optionally start the first child.
disable-model-invocation
true
issue-flow-version
0.4.2a4

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):

  1. Explicit hints in slash input — root:<path>, repo:<folder-basename> (directory name, e.g. cellpy-core), or repo:owner/name.
  2. 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.
  3. Branch context — exactly one workspace repo whose branch matches ^\d+- → that root.
  4. Single scaffold — exactly one .issueflows/ tree visible in the workspace → that root.
  5. 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.
  6. Ambiguous → stop and ask; never guess between sibling repos.

After resolution, treat the result as <project_root> and <owner/repo>:

  • Git: git -C <project_root> … (or issue-flow agent … -C <project_root> for supported ops).
  • GitHub: pass an explicit repo on every gh call — never rely on gh's implicit cwd default. For most commands use --repo <owner/repo>; exception: gh repo view takes the repo as a positional arg (gh repo view <owner/repo> …) and rejects --repo.
  • Paths: all .issueflows/… paths are under <project_root>.

When .issueflows/04-designs-and-guides/multi-repo-workspaces.md exists, read it for layout and cross-repo guidance.

Instructions

Phase 1 — draft children
  1. Resolve parent N. Trailing number, else the single issue<n>_original.md in .issueflows/01-current-issues/, else leading digits of a ^\d+-.+ branch. Ambiguous or missing → stop and ask.
  2. Preflight. Detect the default branch (gh repo view --json defaultBranchRef -q .defaultBranchRef.name; fall back to git symbolic-ref --quiet --short refs/remotes/origin/HEAD, else main). Run git fetch --prune. Report current branch + clean/dirty tree. Creating children does not require a clean tree; branching onto a child later does.
  3. Draft 2–5 children. Propose titles + light bodies (not a full /iflow-plan):
    • Problem / context
    • Spec
    • Acceptance criteria
    • Out of scope (optional; omit the heading when empty) Each body ends with Sub-issue of #<N>. Refine until the user confirms the set.
  4. Size gate. If the cut wants sequential stages or explicit Depends on lines → stop. Recommend /iflow-epic. Do not create.
Show full SKILL.md (388 more words)Show less
  1. Consolidated confirm (normal prose, never shortened). One prompt covering: parent #N stays open as the tracker; each listed child title will be created; each will be linked as a GitHub native sub-issue; a - [ ] #<M> task-list block will be appended on the parent under ## Sub-issues. No yes → stop.
  2. Create + link (idempotent). For each unpublished child:

    1. gh issue create --repo <owner/repo> (labels/milestones only if the user asked this turn). Capture number M.

    2. Link as a native sub-issue. Prefer the CLI fast path: issue-flow agent sub-issue-add <N> <M> -C <project_root> [--repo owner/repo] --json Fields: linked, skipped (already a child), error. On CLI missing or error set, fall back to the REST recipe below — then if that also fails (404 / permission / plan), keep the created issue and rely on the parent task list.

    3. REST recipe (single source — other skills point here; do not copy): sub_issue_id is the child's numeric database id, not the issue number. gh api -f stringifies and 422s. Send JSON:

      bash
      CHILD_ID=$(gh api repos/<owner>/<repo>/issues/<M> --jq .id)
echo "{\"sub_issue_id\": ${CHILD_ID}}" | \
  gh api repos/<owner>/<repo>/issues/<N>/sub_issues -X POST --input -

      Re-runs: GET repos/<owner>/<repo>/issues/<N>/sub_issues (or the CLI skipped field) — skip children already linked.

    4. Append - [ ] #<M> under a ## Sub-issues heading on the parent (gh issue edit <N> --body-file, append/patch only — never rewrite the user's own body). Task list is the fallback when the sub-issue API is unavailable.

    5. Record created numbers in the parent's local status file (create it if missing) so a later re-run can skip them.

  3. Local parent. If issue<N>_* is in .issueflows/01-current-issues/, move the whole group to .issueflows/02-partly-solved-issues/. Status checkbox stays - [ ] Done. Do not close the GitHub parent. Do not write issue<M>_* groups for children.
Phase 3 — optional handoff
  1. Ask whether to start the first child: /iflow-pick-style branch <M>-<slug> off the default (clean-tree gate) + /iflow-capture for M. Do not auto-run /iflow-plan or /iflow-build. Declining leaves the children as open GitHub issues for a later pick.

Constraints

  • Off-path: never auto-dispatch from /iflow, /iflow-build, or /iflow-close.
  • Never create a GitHub issue or sub-issue link without the consolidated confirm; show titles and bodies first.
  • GitHub only (gh / gh api); GitLab is not supported.
  • Parent stays open. Do not convert the parent into an epic plan file.
  • Do not merge with /iflow-epic publish or /iflow-issue — different intents.
  • Do not park generated children under 02-partly-solved-issues/.

© jepegit, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .cursor/skills/iflow-split of jepegit/cellpy.

Open the folder on GitHubat commit ff2c665

Compare with similar skills

Iflow Split next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Iflow Split compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Iflow Split this skilljepegit/cellpy110—~1.8kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Diagnosing Superpowers Sessionsobra/superpowers296k3 repos~1.7kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow83k5 repos~1.3kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Diagnosing Superpowers Sessions

    obra/superpowers

    Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    296k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    83k GitHub starsUsed in 5 repos~1.3k tokens
    Research & ScienceAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed

  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.8k tokensUpdated today
    Research & ScienceAuto-check: notes

More from jepegit/cellpy

All 13 skills in this repo

  • Gh CI

    jepegit/cellpy

    Use GitHub CLI to snapshot or wait on CI for a pull request or workflow run.

    110 GitHub stars~667 tokensUpdated 2 days ago
    Auto-check passed

  • Caveman

    jepegit/cellpy

    Respond in a terse "smart caveman" style that keeps all technical substance but drops filler, articles, and pleasantries.

    110 GitHub stars~725 tokensUpdated 2 days ago
    Auto-check passed

  • Grill Me

    jepegit/cellpy

    Interview the user relentlessly about a plan or design until every branch of the decision tree is resolved, then feed the conclusions into the issue plan.

    110 GitHub stars~676 tokensUpdated 2 days ago
    Auto-check passed

  • Iflow Archive

    jepegit/cellpy

    Condense old solved issue groups into one dated summary file, then delete the originals.

    110 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Iflow Capture

    jepegit/cellpy

    Capture a GitHub issue locally as issue<numberoriginal.md and archive other current issues by done status.

    110 GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

  • Iflow Comments

    jepegit/cellpy

    Triage a GitHub issue's comment thread into the curated, bucketed summary section of issue<Noriginal.md.

    110 GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about Iflow Split

What does Iflow Split do?

Split one over-large GitHub issue into linked child issues (native sub-issues), then optionally start the first child. Iflow Split is an agent skill from jepegit/cellpy. Split one over-large GitHub issue into linked child issues (native sub-issues), then optionally start the first child.

How do I install Iflow Split in Claude Code?

Run `npx skills add jepegit/cellpy --skill iflow-split -a claude-code`. Or copy the skill folder (.cursor/skills/iflow-split in jepegit/cellpy) into .claude/skills/iflow-split in your project. Claude Code loads it when a task matches its description.

How do I install Iflow Split in Codex?

Run `npx skills add jepegit/cellpy --skill iflow-split -a codex`. Or copy the skill folder (.cursor/skills/iflow-split in jepegit/cellpy) into .agents/skills/iflow-split in your project. Codex loads it when a task matches its description.

Can I use Iflow Split in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jepegit/cellpy --skill iflow-split -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iflow-split, .gemini/skills/iflow-split, .github/skills/iflow-split and .opencode/skills/iflow-split in your project.

What does Iflow Split need to run?

Going by SKILL.md and its folder, Iflow Split needs the command-line tools its instructions call (gh and git).

Does Iflow Split access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Iflow Split safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Iflow Split use?

Iflow Split is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Iflow Split use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Iflow Split?

Skills that share tags, products or a category with Iflow Split: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Iflow Split?

jepegit (a GitHub user) maintains it in jepegit/cellpy, which has 110 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 6, 2026.

Source: jepegit/cellpy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.