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 Pause

by jepegit in jepegit/cellpy

Park work on the current issue without closing it: update status, move the group to 02-partly-solved-issues/, optional WIP commit.

MITAuto-check passedDevelopment

Install Iflow Pause

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

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

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

At a glance

Park work on the current issue without closing it: update status, move the group to 02-partly-solved-issues/, optional WIP commit.

  • 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 Instructions and Constraints
  • Calls git and gh

What it does

Iflow Pause is an agent skill from jepegit/cellpy. Park work on the current issue without closing it: update status, move the group to 02-partly-solved-issues/, optional WIP commit.

Its SKILL.md is about 1.2k 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-pause”

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:

    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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 Pause loads about 1.2k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 587 words of instructions outside code blocks.

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

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). 587 words, ~1,160 tokens.

Download SKILL.mdSave it as .claude/skills/iflow-pause/SKILL.md (or your agent's skills folder).
name
iflow-pause
description
Park work on the current issue without closing it: update status, move the group to 02-partly-solved-issues/, optional WIP commit.
disable-model-invocation
true
issue-flow-version
0.4.2a4

issue-flow — issue pause (/iflow-pause)

Follow this skill to park work on the current issue without closing it. The issue is not done — this is not /iflow-close.

Invoke: type iflow pause in chat, or /iflow-pause from the slash menu (iflow-pause 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.

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.

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

Instructions

  1. Find the focus issue. In .issueflows/01-current-issues/, identify the issue<N>_* group. If multiple groups exist and the focus is ambiguous, ask. If none exist, stop and say there is nothing to pause.

  2. Update issue<N>_status.md. Create or update it under .issueflows/01-current-issues/ with:

    • - [ ] Done (must remain unchecked — a pause is not a close).
    • Done so far — short bullets of what has landed or been tried.
    • Remaining work — explicit next steps so work can resume later.
    • Paused on — date, branch name, any blockers.

    Preserve earlier user-written content; only add or update these sections. If the user passed a short note after /iflow-pause, use it verbatim as the Remaining work text.

  3. Move the issue group. Move every issue<N>_* file from .issueflows/01-current-issues/ to .issueflows/02-partly-solved-issues/. Report each move.

  4. Working-tree guard. Run git status --porcelain. Report what is dirty, then offer — as one consolidated prompt — any combination of:

    • WIP commit — stage tracked changes and commit WIP: pause issue #<N> — <short note>. List untracked files separately and ask before including them.
    • Switch to default branch — detect default (prefer gh repo view --json defaultBranchRef -q .defaultBranchRef.name, else git symbolic-ref --quiet --short refs/remotes/origin/HEAD, else main) and run git switch <default>. Only after the WIP commit if the tree is dirty.
    • Stay put — leave branch and working tree untouched.

  5. Report. Summarize the status update, the issue-group moves, working-tree actions taken, and remind the user how to resume (running /iflow-capture <N> re-opens the archived issue after its archived-issue guard, or they can simply switch back to the issue branch).

Constraints

  • The focus issue's - [ ] Done checkbox must stay unchecked. /iflow-pause is not /iflow-close.
  • Do not delete branches. Do not git reset, git stash drop, or force-push.
  • Do not open a PR. Do not bump versions. Do not run tests.

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

Open the folder on GitHubat commit ff2c665

Compare with similar skills

Iflow Pause 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 Pause compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Iflow Pause this skilljepegit/cellpy109—~1.2kAutomated 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 Pause

What does Iflow Pause do?

Park work on the current issue without closing it: update status, move the group to 02-partly-solved-issues/, optional WIP commit. Iflow Pause is an agent skill from jepegit/cellpy. Park work on the current issue without closing it: update status, move the group to 02-partly-solved-issues/, optional WIP commit.

When should I use Iflow Pause?

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

How do I install Iflow Pause in Claude Code?

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

How do I install Iflow Pause in Codex?

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

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

What does Iflow Pause need to run?

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

Does Iflow Pause access the network?

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

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

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

About 1.2k tokens (SKILL.md is roughly 4.6k 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 Pause?

Skills that share tags, products or a category with Iflow Pause: 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 Pause?

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.