Install the "iflow-pr-sync" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-pr-sync into .claude/skills/iflow-pr-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-pr-sync", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add jepegit/cellpy --skill iflow-pr-sync -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "iflow-pr-sync" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-pr-sync into .agents/skills/iflow-pr-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-pr-sync", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add jepegit/cellpy --skill iflow-pr-sync -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "iflow-pr-sync" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-pr-sync into .cursor/skills/iflow-pr-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-pr-sync", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add jepegit/cellpy --skill iflow-pr-sync -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "iflow-pr-sync" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-pr-sync into .gemini/skills/iflow-pr-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-pr-sync", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
GitHub CLI
$ gh skill install jepegit/cellpy iflow-pr-sync
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add jepegit/cellpy --skill iflow-pr-sync -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "iflow-pr-sync" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-pr-sync into .github/skills/iflow-pr-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-pr-sync", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add jepegit/cellpy --skill iflow-pr-sync -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "iflow-pr-sync" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-pr-sync into .opencode/skills/iflow-pr-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-pr-sync", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
iflow-pr-sync
GitHub stars
110
Token cost
~1.2k tokens
SKILL.md length
557 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT
At a glance
Refresh open PR heads onto the default branch after another merge left them DIRTY (usually HISTORY.md).
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 Input, Instructions and Constraints
Calls git and gh
What it does
Iflow PR Sync is an agent skill from jepegit/cellpy. Refresh open PR heads onto the default branch after another merge left them DIRTY (usually HISTORY.md). Uses sync-branch keep-both + force-with-lease.
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-pr-sync”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
1Explicit hints in slash input — root:, repo: (directory name, e.g. cellpy-core), or repo:owner/name.
2CLI fast path — issue-flow agent resolve [-C ] [--from-file ] [--json]. Use the returned project_root and repo; pass -C to other…
3Branch context — exactly one workspace repo whose branch matches ^\d+- → that root.
4Single scaffold — exactly one .issueflows/ tree visible in the workspace → that root.
5Workspace default — an issueflow-workspace.toml at the workspace root (created with issue-flow workspace init) may name a default member…
6Ambiguous → 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 PR Sync loads about 1.2k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 557 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~41
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.
Download SKILL.mdSave it as .claude/skills/iflow-pr-sync/SKILL.md (or your agent's skills folder).
name
iflow-pr-sync
description
Refresh open PR heads onto the default branch after another merge left them DIRTY (usually HISTORY.md). Uses sync-branch keep-both + force-with-lease.
disable-model-invocation
true
issue-flow-version
0.4.2a4
issue-flow — PR queue sync (/iflow-pr-sync)
Follow this skill when one or more open PRs need updating after another PR
merged — typically mergeable: CONFLICTING / mergeStateStatus: DIRTY because
both sides edited HISTORY.md.
Do not use this from /iflow. Off-path only. Sibling of /iflow-cleanup
(post-merge local hygiene) and of issue-flow agent sync-branch (single branch).
Invoke: type iflow pr-sync in chat, or /iflow-pr-sync from the slash menu (iflow-pr-sync 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):
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.
After resolution, treat the result as <project_root> and <owner/repo>:
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.
Input
(nothing) — refresh every open PR GitHub marks as needing update (DIRTY /
BEHIND / CONFLICTING).
PR numbers — e.g. /iflow-pr-sync 259 261 — only those heads.
dry-run / dryrun — list candidates; do not sync or push.
nopush / no-push — sync locally but do not push.
all — every open PR, not only dirty ones (rare).
Show full SKILL.md (215 more words)Show less
Instructions
Preflight. Resolve <project_root> / <owner/repo>. Prefer standing on
the default branch with a clean home tree (worktrees are used for each
head). git fetch --prune.
List candidates. Prefer CLI:bash
issue-flow agent pr-sync --dry-run --json -C <project_root>
# or with numbers:
issue-flow agent pr-sync 259 261 --dry-run --json -C <project_root>
Show the user: PR number, head branch, mergeable / mergeStateStatus, URL.
Confirm once. Consolidated yes/no listing every head that will be
rebased (or merged) onto origin/<default> and force-with-lease pushed.
Decline → stop; nothing rewritten.
Honour trailing nopush / dry-run / all as flags (--no-push,
--dry-run, --all-open). Default is --fail-fast: first non-HISTORY /
non-keep-both conflict stops the batch and leaves later PRs untouched.
Report. Per PR: synced / pushed / changelog_resolved / failure notes.
Remind that CI must re-run on rewritten heads. Do not auto-merge.
When to offer. After /iflow-cleanup when other open PRs remain dirty;
after /iflow-yolo / /iflow-close merge when siblings are open; whenever
the user says a PR “needs update” and the only conflict is changelog-shaped.
Constraints
Off-path; never auto-dispatch from /iflow.
Never bare --force; only --force-with-lease via the CLI.
Never --admin merge; never skip required checks.
Non-changelog / heading-promote conflicts → stop that head (and the batch
under fail-fast); human decides.
Prevention (defer_changelog) is separate — see
.issueflows/04-designs-and-guides/pr-queue-sync.md.
Iflow PR Sync 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.
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.
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
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.
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.
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.
Refresh open PR heads onto the default branch after another merge left them DIRTY (usually HISTORY.md). Iflow PR Sync is an agent skill from jepegit/cellpy.md).
When should I use Iflow PR Sync?
Iflow PR Sync fits situations like: development work in your project.
How do I install Iflow PR Sync in Claude Code?
Run `npx skills add jepegit/cellpy --skill iflow-pr-sync -a claude-code`. Or copy the skill folder (.cursor/skills/iflow-pr-sync in jepegit/cellpy) into .claude/skills/iflow-pr-sync in your project. Claude Code loads it when a task matches its description.
How do I install Iflow PR Sync in Codex?
Run `npx skills add jepegit/cellpy --skill iflow-pr-sync -a codex`. Or copy the skill folder (.cursor/skills/iflow-pr-sync in jepegit/cellpy) into .agents/skills/iflow-pr-sync in your project. Codex loads it when a task matches its description.
Can I use Iflow PR Sync 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-pr-sync -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-pr-sync, .gemini/skills/iflow-pr-sync, .github/skills/iflow-pr-sync and .opencode/skills/iflow-pr-sync in your project.
What does Iflow PR Sync need to run?
Going by SKILL.md and its folder, Iflow PR Sync needs the command-line tools its instructions call (git and gh).
Does Iflow PR Sync 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 PR Sync 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 PR Sync use?
Iflow PR Sync 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 PR Sync use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 PR Sync?
Skills that share tags, products or a category with Iflow PR Sync: 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, 86k 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 PR Sync?
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.
