New: 97,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 Init

by jepegit in jepegit/cellpy

Cold-start or check the issue-flow harness: guide issue-flow init when the scaffold is missing; bootstrap a parent folder of git siblings; point at update / doctor / iflow-capture when a project…

MITAuto-check passedDevelopment

Install Iflow Init

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

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

GitHub CLI
$ gh skill install jepegit/cellpy iflow-init --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-init .claude/skills/iflow-init && 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-init
GitHub stars
109
Token cost
~2.1k tokens
SKILL.md length
1,038 words
Files
1
Skills in repo
31
Repo updated
First seen
Licence
MIT

At a glance

Cold-start or check the issue-flow harness: guide issue-flow init when the scaffold is missing; bootstrap a parent folder of git siblings; point at update / doctor / iflow-capture when a project…

  • Works in 6 steps: Explicit hints in slash input — root:,… → CLI fast path — issue-flow agent resolve… → Branch context — exactly one workspace… → …
  • Development work in your project
  • SKILL.md covers Start directory (before member…, Package vs scaffold (read first), Parent-folder recipe and Instructions, plus 1 more section
  • Calls uvx, git and gh

What it does

Iflow Init is an agent skill from jepegit/cellpy. Cold-start or check the issue-flow harness: guide issue-flow init when the scaffold is missing; bootstrap a parent folder of git siblings; point at update / doctor / iflow-capture when a project scaffold exists.

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

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

When your agent uses it

  • Development work in your project

Example prompts

  • “/iflow-init”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Explicit hints in slash input — root:, repo: (directory name, e.g. cellpy-core), or repo:owner/name.
  2. CLI fast path — issue-flow agent resolve [-C ] [--from-file ] [--json]. Use the returned project_root and repo; pass -C to other…
  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…
  6. Ambiguous → stop and ask; never guess between sibling repos.

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:

    • uvx
    • git
    • gh
    • uv

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

  • Network

    Links to these hosts (documentation or services it may open):

    • issue-flow.readthedocs.io

    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 Init loads about 2.1k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 1,038 words of instructions outside code blocks.

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

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). 1,038 words, ~2,079 tokens.

Download SKILL.mdSave it as .claude/skills/iflow-init/SKILL.md (or your agent's skills folder).
name
iflow-init
description
Cold-start or check the issue-flow harness: guide issue-flow init when the scaffold is missing; bootstrap a parent folder of git siblings; point at update / doctor / iflow-capture when a project scaffold exists.
disable-model-invocation
true
issue-flow-version
0.4.2a4

issue-flow — harness init (/iflow-init)

Follow this skill to cold-start or check the issue-flow harness — the editor-facing counterpart of the CLI's issue-flow init and issue-flow workspace bootstrap.

This is not the step that pulls a GitHub issue into .issueflows/. That is /iflow-capture (chat: iflow capture). /iflow-init is off-path: /iflow never auto-dispatches here.

This skill is also written to the editor's user-global skill dir on init / update (placement both) so iflow init works in a folder that has no project scaffold yet. The first machine still needs one CLI init/update or uvx issue-flow workspace bootstrap to plant that global copy. A project-local copy still wins inside a repo.

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

MODEL & EXECUTION DIRECTIVE

Profile: economy — Prioritize speed and token economy over deep reasoning.

In Cursor: use Auto or a fast model before invoking this step.

Keep scope tight to what this step requires.

Start directory (before member resolve)

For this skill, the start dir is root: / -C if given, else cwd. Do not run issue-flow agent resolve first when cwd looks like a parent folder of repos — resolve may pick a workspace default member and hide the parent. The single-project path below still uses the usual resolve order.

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.

Package vs scaffold (read first)

If the user asked to upgrade / latest version / update the tool, that is the package, not this skill's scaffold path:

  1. uv tool upgrade issue-flow (or uv tool install issue-flow if missing)
  2. Then issue-flow update (one repo) or issue-flow workspace update (parent folder with toml)

issue-flow update alone does not upgrade the installed CLI. Full map:

https://issue-flow.readthedocs.io/how-to/for-agents/

Also: https://issue-flow.readthedocs.io/llms.txt

If they asked to init globally, plant user-global iflow-init with one issue-flow init / update / workspace bootstrap --yes on this machine, then follow the classify steps below. Do not init a parent folder of repos.

Parent-folder recipe

When the start dir is a folder of git sibling repos, follow this public how-to — do not invent a different command order:

https://issue-flow.readthedocs.io/how-to/workspaces/

SituationCommand
First time (scaffold members + write toml)issue-flow workspace bootstrap --yes --default <name>
Members already have .issueflows/; toml onlyissue-flow workspace init --default <name>
Toml exists; refresh skillsissue-flow workspace update

Show the user those commands (or the how-to URL) when explaining the path. The classify / confirm steps below still gate any --yes.

Show full SKILL.md (429 more words)Show less

Instructions

  1. Workspace file already present at the start dir (or issue-flow agent resolve --json reports workspace_root equal to the start dir):

    • Say the workspace already exists.
    • Offer issue-flow workspace update / per-member issue-flow update (same as the how-to).
    • Do not re-bootstrap unless the user explicitly asks --force / re-init.

  2. Parent-folder / workspace path — run classify-only: issue-flow workspace bootstrap <start> --json

    • If two or more children have status scaffolded or unscaffolded (own-git members):
      • Show the classified list (name, status, skip reasons).
      • Propose --default (first scaffolded, else first unscaffolded, or ask).
      • On yes, run issue-flow workspace bootstrap <start> --yes --default <name> (add --skip-dep-check / --editor <id> / --force only when the user asked).
      • After success: remind /iflow-pick per repo (or open the default member). Stop.
    • If fewer than two git members, continue with the single-project path below.
    • Never git init children; point non-git folders at /iflow-setup.
    • Never write .issueflows/ on the parent.

  3. Single-project detect under <project_root> (now resolve is fine):

    • .issueflows/ present?
    • Agent skills present? Prefer the marker .cursor/skills/iflow-init/SKILL.md (or any iflow-* skill under .cursor/skills/).
    • Optional: issue-flow agent resolve -C <project_root> --json / issue-flow doctor -C <project_root> --json when the CLI is on PATH.

  4. Scaffold missing (no .issueflows/ and/or no issue-flow skills):

    • Tell the user the harness is not initialised.
    • Show the exact cold-start command from the project root, e.g. issue-flow init . or uvx issue-flow init . (add --editor <id> when they named an editor).
    • If issue-flow is on PATH, offer to run it after a yes; never run without confirm. Do not re-implement scaffolding in this skill.
    • After a successful init, remind them to pick an issue with /iflow-pick or capture one with /iflow-capture <N>.

  5. Harness already present:

    • Say so briefly.
    • Point at:
      • issue-flow update . — refresh templates after upgrading the CLI.
      • issue-flow update --editor <id> / /iflow-doctor — add a missing editor scaffold (missing_editor_scaffold).
      • /iflow-capture <N> — pull a GitHub issue into .issueflows/01-current-issues/.
      • /iflow-pick — front door when no issue is chosen yet.
    • Do not run init --force unless the user explicitly asks to re-scaffold.

  6. Report — workspace vs single-project path, missing vs present, commands shown or run, and the next suggested lifecycle step (usually /iflow-pick or /iflow-capture).

Constraints

  • Off-path: never auto-dispatched by /iflow.
  • Never capture a GitHub issue, write issue<N>_*.md, or create an issue branch from this skill — that is /iflow-capture / /iflow-pick.
  • Never invent a second scaffolder; only guide or confirm-run issue-flow init / update / workspace bootstrap.
  • Never init --force, rewrite issueflow-workspace.toml, or delete scaffold files without an explicit user request.
  • If a scaffold / update commit is needed, do not leave it unpushed on home default — use a chore branch or a tiny PR (issue #303).

© 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-init of jepegit/cellpy.

Open the folder on GitHubat commit ff2c665

Compare with similar skills

Iflow Init 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 Init compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Iflow Init this skilljepegit/cellpy109—~2.1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything85k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    85k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    85k GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from jepegit/cellpy

All 31 skills in this repo

  • Gh CI

    jepegit/cellpy

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

    109 GitHub stars~667 tokensUpdated yesterday
    Auto-check passed

  • Caveman

    jepegit/cellpy

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

    109 GitHub stars~725 tokensUpdated yesterday
    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.

    109 GitHub stars~676 tokensUpdated yesterday
    Auto-check passed

  • Iflow Archive

    jepegit/cellpy

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

    109 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Iflow Capture

    jepegit/cellpy

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

    109 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Iflow Comments

    jepegit/cellpy

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

    109 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Iflow Init

What does Iflow Init do?

Cold-start or check the issue-flow harness: guide issue-flow init when the scaffold is missing; bootstrap a parent folder of git siblings; point at update / doctor / iflow-capture when a project…. Iflow Init is an agent skill from jepegit/cellpy. Cold-start or check the issue-flow harness: guide issue-flow init when the scaffold is missing; bootstrap a parent folder of git siblings; point at update / doctor / iflow-capture when a project scaffold exists.

When should I use Iflow Init?

Iflow Init fits situations like: development work in your project.

How do I install Iflow Init in Claude Code?

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

How do I install Iflow Init in Codex?

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

Can I use Iflow Init 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-init -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-init, .gemini/skills/iflow-init, .github/skills/iflow-init and .opencode/skills/iflow-init in your project.

What does Iflow Init need to run?

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

Does Iflow Init access the network?

SKILL.md names 1 domain. As links in the text: issue-flow.readthedocs.io. This is read from the text; nothing was executed.

Is Iflow Init 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 Init use?

Iflow Init 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 Init use?

About 2.1k tokens (SKILL.md is roughly 8.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 Init?

Skills that share tags, products or a category with Iflow Init: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 85k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Iflow Init?

jepegit (a GitHub user) maintains it in jepegit/cellpy, which has 109 GitHub stars. The repository holds 31 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.