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.
Triage a GitHub issue's comment thread into the curated, bucketed summary section of issue<Noriginal.md.
MITAuto-check passed
Install Iflow Comments
$ npx skills add jepegit/cellpy --skill iflow-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jepegit/cellpy iflow-comments --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jepegit/cellpy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/iflow-comments .claude/skills/iflow-comments && rm -rf skills-srcUse ~/.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/
Install the "iflow-comments" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-comments into .claude/skills/iflow-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-comments", 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.
$skill-installer install https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-commentsType 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.
$ npx skills add jepegit/cellpy --skill iflow-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jepegit/cellpy iflow-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jepegit/cellpy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/iflow-comments .agents/skills/iflow-comments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "iflow-comments" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-comments into .agents/skills/iflow-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-comments", 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.
$ npx skills add jepegit/cellpy --skill iflow-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jepegit/cellpy iflow-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jepegit/cellpy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/iflow-comments .cursor/skills/iflow-comments && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "iflow-comments" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-comments into .cursor/skills/iflow-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-comments", 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.
$ gemini skills install https://github.com/jepegit/cellpy.git --path .cursor/skills/iflow-comments--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jepegit/cellpy --skill iflow-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jepegit/cellpy iflow-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jepegit/cellpy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/iflow-comments .gemini/skills/iflow-comments && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "iflow-comments" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-comments into .gemini/skills/iflow-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-comments", 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.
$ gh skill install jepegit/cellpy iflow-commentsInstalls 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).
$ npx skills add jepegit/cellpy --skill iflow-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jepegit/cellpy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/iflow-comments .github/skills/iflow-comments && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "iflow-comments" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-comments into .github/skills/iflow-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-comments", 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.
$ npx skills add jepegit/cellpy --skill iflow-comments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jepegit/cellpy iflow-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jepegit/cellpy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/iflow-comments .opencode/skills/iflow-comments && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "iflow-comments" agent skill from https://github.com/jepegit/cellpy/tree/master/.cursor/skills/iflow-comments into .opencode/skills/iflow-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iflow-comments", 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-comments- GitHub stars
- 109
- Token cost
- ~1.4k tokens
- SKILL.md length
- 719 words
- Files
- 1
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
Triage a GitHub issue's comment thread into the curated, bucketed summary section of issue<Noriginal.md.
- Works in 7 steps: Chronological precedence. Walk the… → Three buckets, pick exactly one per… → Drop the noise. Do not include → …
- SKILL.md covers Inputs, Triage rules, Output contract and Edge cases, plus 1 more section
- Calls gh
What it does
Iflow Comments is an agent skill from jepegit/cellpy. Triage a GitHub issue's comment thread into the curated, bucketed summary section of issue<Noriginal.md.
Its SKILL.md is about 1.4k 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-comments”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Chronological precedence. Walk the comments oldest → newest. If a later comment contradicts or walks back an earlier point, the earlier…
- Three buckets, pick exactly one per surviving point.
- Drop the noise. Do not include
- Collapse duplicates. If two commenters make the same point, record it once.
- Paraphrase; quote sparingly. Short direct quotes are fine when exact wording matters (e.g. a feature name, an error message). Otherwise…
- Handle open disagreement honestly. If two authors openly disagree and no later comment resolves it, record the disagreement under…
- Respect maintainer authority when obvious. If the repo owner or a maintainer explicitly overrides an earlier suggestion, treat that as the…
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
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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 Comments loads about 1.4k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 719 words of instructions outside code blocks.
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). 719 words, ~1,424 tokens.
Download SKILL.mdSave it as
.claude/skills/iflow-comments/SKILL.md (or your agent's skills folder).- name
- iflow-comments
- description
- Triage a GitHub issue's comment thread into the curated, bucketed summary section of issue<N>_original.md.
- disable-model-invocation
- true
- issue-flow-version
- 0.4.2a4
issue-flow — issue comments triage
Follow this skill to turn a GitHub issue's comment thread into a short, decision-useful summary that lives next to the original issue body under .issueflows/01-current-issues/issue<N>_original.md.
It is the playbook that /iflow-capture (and the iflow-capture skill) delegate to for anything beyond fetching raw comments. It also covers re-triage of an already-captured issue when new comments arrive (the issue body text stays unchanged; only the curated section is rewritten).
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.
Inputs
A JSON array of comments as returned by:
gh issue view <N> --repo owner/repo --json comments -q .commentsEach element has at least:
author.login— commenter handlebody— markdown textcreatedAt— ISO timestamp
If you only have raw comment text, ask for the structured form (author + date matter for tie-breaking and for the footer).
Triage rules
Chronological precedence. Walk the comments oldest → newest. If a later comment contradicts or walks back an earlier point, the earlier point moves to Superseded / retracted and the later one takes its place in the appropriate bucket.
Three buckets, pick exactly one per surviving point.
- Additional tasks — new, concrete work that is not already in the issue body. Phrase as imperatives ("also update X", "add Y to Z"). If the point is vague ("maybe do something about caching"), either sharpen it into a task or drop it.
- Clarifications / constraints — guidance on how to do the existing work: scope boundaries, non-goals, must-keep behaviors, stylistic or architectural preferences, acceptance criteria. Useful phrase: "when doing X, make sure Y".
- Superseded / retracted — earlier tasks, preferences, or decisions that a later comment explicitly or implicitly walked back. Keep these visible (don't silently delete them) so the agent doesn't redo retracted work.
Drop the noise. Do not include:
- Bot comments (CI, coverage bots, auto-assign bots, etc.).
- Pure chit-chat, "LGTM", "+1", emoji-only reactions.
- Status pings ("any update?") without new content.
- Comments that only quote earlier ones without adding anything.
Collapse duplicates. If two commenters make the same point, record it once.
Paraphrase; quote sparingly. Short direct quotes are fine when exact wording matters (e.g. a feature name, an error message). Otherwise rewrite in your own words so the summary is scannable.
Handle open disagreement honestly. If two authors openly disagree and no later comment resolves it, record the disagreement under Clarifications (for example: "author A prefers option X, author B prefers option Y — no resolution in thread"). Do not guess a winner.
Respect maintainer authority when obvious. If the repo owner or a maintainer explicitly overrides an earlier suggestion, treat that as the winning position and move the overridden suggestion to Superseded.
Show full SKILL.md (268 more words)Show less
Output contract
Write exactly this block into issue<N>_original.md, immediately after the ## Original issue text section:
## Comments (curated summary)
- **Additional tasks**: <bullets distilled from comments that add real work>
- **Clarifications / constraints**: <bullets the agent should honour>
- **Superseded / retracted**: <earlier points later contradicted or walked back>
_Note: this section is an interpretive summary of the comment thread, not a verbatim dump. Source comments: <count>, last comment by @<login> on <date>._Formatting rules:
- Each bucket's bullet is itself a list if there is more than one item — nest concrete bullets under the bold label.
- Drop any bucket that is empty — do not leave
- **Additional tasks**:with no content. - Always keep the
_Note: ..._footer when the section exists. Use the totalcommentslength for<count>and theauthor.login+ date of the most recent non-dropped comment for@<login>/<date>.
Edge cases
- Zero comments — skip the whole section. Do not write an empty
## Comments (curated summary)header. - All comments are noise (bot-only, pure chit-chat, emoji) — skip the whole section. Note this in the command's final report ("N comments fetched, all filtered as noise — section omitted").
- Every surviving point lands in a single bucket — that's fine; just emit that one bucket.
- Multi-author thread with heated disagreement — log the disagreement under Clarifications, do not invent a resolution.
- Comments reference external PRs, gists, or linked issues — keep the reference (shortened URL or
owner/repo#N) in the bullet, but do not fetch the linked content; it's out of scope for this skill. - Comments include code blocks the agent will need later — summarize the intent in the bullet and mention that the full snippet is in the linked comment; do not paste large blocks into the summary.
Constraints
- This skill only writes into the
## Comments (curated summary)section ofissue<N>_original.md. It never touches the issue body, the status file, or the plan file. - It never calls
ghor the network itself — it expects the caller (/iflow-captureor similar) to provide the comments JSON.
© 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-comments of jepegit/cellpy.
Open the folder on GitHubat commit ff2c665
Compare with similar skills
Iflow Comments 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Iflow Comments this skilljepegit/cellpy | 109 | — | ~1.4k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Superpowers Sessionsobra/superpowers | 296k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 83k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 |
Similar skills
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.
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.
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.
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.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
More from jepegit/cellpy
All 31 skills in this repoGh CI
jepegit/cellpy
Use GitHub CLI to snapshot or wait on CI for a pull request or workflow run.
Caveman
jepegit/cellpy
Respond in a terse "smart caveman" style that keeps all technical substance but drops filler, articles, and pleasantries.
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.
Iflow Archive
jepegit/cellpy
Condense old solved issue groups into one dated summary file, then delete the originals.
Iflow Capture
jepegit/cellpy
Capture a GitHub issue locally as issue<numberoriginal.md and archive other current issues by done status.
Iflow Epic
jepegit/cellpy
Plan a larger change as a staged epic: draft epic<Nplan.md with stages of manageable issue specs, then publish confirmed stages as GitHub issues.
Related
Works with
Questions about Iflow Comments
What does Iflow Comments do?
Triage a GitHub issue's comment thread into the curated, bucketed summary section of issue<Noriginal.md. Iflow Comments is an agent skill from jepegit/cellpy.md.
How do I install Iflow Comments in Claude Code?
Run `npx skills add jepegit/cellpy --skill iflow-comments -a claude-code`. Or copy the skill folder (.cursor/skills/iflow-comments in jepegit/cellpy) into .claude/skills/iflow-comments in your project. Claude Code loads it when a task matches its description.
How do I install Iflow Comments in Codex?
Run `npx skills add jepegit/cellpy --skill iflow-comments -a codex`. Or copy the skill folder (.cursor/skills/iflow-comments in jepegit/cellpy) into .agents/skills/iflow-comments in your project. Codex loads it when a task matches its description.
Can I use Iflow Comments 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-comments -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-comments, .gemini/skills/iflow-comments, .github/skills/iflow-comments and .opencode/skills/iflow-comments in your project.
What does Iflow Comments need to run?
Going by SKILL.md and its folder, Iflow Comments needs the command-line tools its instructions call (gh).
Does Iflow Comments access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Iflow Comments 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 Comments use?
Iflow Comments 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 Comments use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Comments?
Skills that share tags, products or a category with Iflow Comments: 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 Comments?
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.