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.
Comprehensive codebase assessment for agent and production readiness.
Install Flow Next Prime
$ npx skills add gmickel/flow-next --skill flow-next-prime -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gmickel/flow-next flow-next-prime --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/gmickel/flow-next.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-prime .claude/skills/flow-next-prime && 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 "flow-next-prime" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-prime into .claude/skills/flow-next-prime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-prime", 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/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-primeType 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 gmickel/flow-next --skill flow-next-prime -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gmickel/flow-next flow-next-prime --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-prime .agents/skills/flow-next-prime && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "flow-next-prime" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-prime into .agents/skills/flow-next-prime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-prime", 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 gmickel/flow-next --skill flow-next-prime -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gmickel/flow-next flow-next-prime --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-prime .cursor/skills/flow-next-prime && 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 "flow-next-prime" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-prime into .cursor/skills/flow-next-prime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-prime", 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/gmickel/flow-next.git --path plugins/flow-next/skills/flow-next-prime--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 gmickel/flow-next --skill flow-next-prime -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gmickel/flow-next flow-next-prime --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-prime .gemini/skills/flow-next-prime && 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 "flow-next-prime" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-prime into .gemini/skills/flow-next-prime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-prime", 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 gmickel/flow-next flow-next-primeInstalls 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 gmickel/flow-next --skill flow-next-prime -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-prime .github/skills/flow-next-prime && 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 "flow-next-prime" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-prime into .github/skills/flow-next-prime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-prime", 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 gmickel/flow-next --skill flow-next-prime -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gmickel/flow-next flow-next-prime --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-prime .opencode/skills/flow-next-prime && 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 "flow-next-prime" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-prime into .opencode/skills/flow-next-prime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-prime", 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
flow-next-prime- GitHub stars
- 709
- Token cost
- ~2.1k tokens
- SKILL.md length
- 1,040 words
- Files
- 12 (incl. references)
- Skills in repo
- 43
- Repo updated
- First seen
- Licence
- MIT
At a glance
Comprehensive codebase assessment for agent and production readiness.
- /flow-next:prime
- SKILL.md covers Two-Tier Assessment, Why This Matters, Input and Route Before Reading References, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Flow Next Prime is an agent skill from gmickel/flow-next. Comprehensive codebase assessment for agent and production readiness. Classifies the project (lifecycle, topology, size, stack, shape), scans 8 pillars, verifies commands actually run, checks GitHub settings. Leads with a verdict + ranked next-actions; fixes agent readiness only. Triggers on /flow-next:prime.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `classification.md`, `harness.md` and `pillars.md`).
It sits in Development. It works with GitHub. The repository describes itself as: Faster than your agent alone. And better. A workflow plugin that takes a bug, idea or ticket to a verified pull request: specs, cross-model review by risk, live QA, receipts in… The licence is MIT.
When your agent uses it
- /flow-next:prime
Example prompts
- “/flow-next-prime”
What it can do on your machine
Read from SKILL.md and the folder at commit c1ce203. 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
No scripts in the folder and no shell commands in SKILL.md.
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):
factory.ai
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
Flow Next Prime loads about 2.1k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 1,040 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 gmickel/flow-next at commit c1ce203, republished under its MIT licence (© gmickel). 1,040 words, ~2,109 tokens.
Download SKILL.mdSave it as
.claude/skills/flow-next-prime/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.- name
- flow-next-prime
- description
- Comprehensive codebase assessment for agent and production readiness. Classifies the project (lifecycle, topology, size, stack, shape), scans 8 pillars, verifies commands actually run, checks GitHub settings. Leads with a verdict + ranked next-actions; fixes agent readiness only. Triggers on /flow-next:prime.
- user-invocable
- false
Flow Prime
Comprehensive codebase assessment inspired by Factory.ai's Agent Readiness framework.
Role: readiness assessor, improvement proposer Goal: full visibility into codebase health, targeted fixes for agent readiness
Read working-rules.md first unless you already have this run; it holds for every step of this skill.
Two-Tier Assessment
| Category | Pillars | What Happens |
|---|---|---|
| Agent Readiness | 1-5 | Scored, maturity level calculated, fixes offered |
| Production Readiness | 6-8 | Reported for awareness, no fixes offered |
This gives you full visibility while keeping remediation focused on what actually helps agents work.
Criteria counts live in pillars.md, never here. pillars.md is the single census source (the legacy scored criteria feeding the maturity level, the informational rows, and the new agent-readiness tier groups AO/DR/TO/HP). Do not restate a count in this file - a hardcoded number drifts the moment a criterion is added. The classification, operability ladder, per-shape playbooks, per-stack matrix, and harness check-set live in the four reference files: classification.md, playbooks.md, stacks.md, harness.md.
Why This Matters
Existence checks lie. A repo can carry a CLAUDE.md, a hook file, and a lint script yet be un-agentic in practice - the file is an empty template, the build is broken, imports don't resolve, or it is really one of 99 sibling repos. Prime judges substance, not existence, and names the single highest-leverage next action.
Agents waste cycles when:
- No closed verify loop → can't confirm a change works without a full CI round-trip; the feedback gate belongs at the RIGHT layer (edit-time/commit format+lint, tests via the verify command + acceptance requirements + CI required check - never a test-running pre-commit hook agents
--no-verifyaround or stall on) - Undocumented env vars → guesses, fails, guesses again
- No agent instruction file (or a generic/stale one) → doesn't know project conventions, the operability tier, or which files are off-limits
- The app can't be built or driven → can't verify changes work; a legacy stack with no headless build has no feedback loop at all
These are environment problems, not agent problems. Prime grades them as layered gates and helps fix the ones that help agents work.
Input
Full request: $ARGUMENTS
Accepts:
- No arguments (scans current repo)
--report-onlyorreport only(skip remediation, just show report)--fix-allorfix all(apply all agent readiness fixes without asking)--classify-onlyorclassify only(print the Phase 0.5 classification block and EXIT - the cheap portfolio-triage sweep over many repos; see classification.md)- A path to a different repo root (first non-flag argument)
Examples:
/flow-next:prime/flow-next:prime --report-only/flow-next:prime --classify-only ~/other-project/flow-next:prime ~/other-project
Resolve ROOT from $ARGUMENTS (the first non-flag token; default .). If ROOT is not the
cwd, resolve it first (ROOT=$(cd "$ROOT" && pwd)), then it MUST thread through everything: cd "$ROOT" before the .flow/meta.json pre-check, the
Phase 0.5 classification probes (the flowctl prime classify emitter takes ROOT as its positional
argument, e.g. flowctl prime classify --json "$ROOT"), and the Phase 2 verification commands; and
every scout dispatch prompt in Phase 1 starts "Assess the repo at ROOT" (scouts scan cwd by default
- without this they'd scan the wrong repo and the report would be confidently wrong end-to-end). If
threading
ROOTisn't feasible, error rather than silently scan cwd.
Route Before Reading References
Parse the mode before loading any reference:
--classify-only: read classification.md directly, run its emitter + judgment-layer contract, print its fixed classification block, and EXIT. Do not readworkflow.md,pillars.md,playbooks.md, orremediation.md; never ask, dispatch scouts, verify, report, or remediate.- All other modes: read workflow.md and execute it. The
workflow loads classification, pillars, playbooks, stacks, harness, and
remediation guidance only at their consuming phases.
--report-onlystops after the report and must never load remediation templates.
This dispatch is fail-open for an unknown/malformed mode: use the full workflow, never silently skip assessment or safety instructions.
Workflow
The mode router above selects the entry reference. Do not pre-read references for branches that will not execute.
Show full SKILL.md (415 more words)Show less
Guardrails
General
- Never modify code files (only config, docs, scripts)
- Never commit changes (leave for user to review)
- Never delete files
- Respect .gitignore patterns
User Consent
- MUST use
AskUserQuestiontool for consent (callToolSearchwithselect:AskUserQuestionfirst if its schema isn't loaded). Never just print questions as text. - Always ask before modifying existing files — except under
--fix-all, which waives the prompt for append/merge edits (adding a.gitignoreline, augmenting an agent file, appending a hook) INCLUDING their required devDependencies for the Critical/High/Medium tiers.--fix-allstill does NOT: overwrite/replace existing file content unseen, touch the Bonus tier (devcontainer, CI workflow — those stay explicit-request-only), or bypass the glossary read-back gate. A destructive overwrite always needs consent even under--fix-all. - Don't add dependencies without consent (a Critical/High/Medium fix's own devDeps are covered by that fix's consent, incl.
--fix-all; never add unrelated deps) - Glossary terms are never written unseen — the Phase 5.5 bootstrap shows the full proposal (term + definition + file-ref evidence) at read-back before any
flowctl glossary add;--fix-alldoes not bypass this gate, and a populated glossary (total_terms > 0) is never rewritten
--fix-all boundaries
--fix-all auto-applies ONLY in-ROOT, non-structural, non-harness fixes at the Critical/High/Medium tier - the in-root Pillars 1-5 fixes PLUS scored-group agent-file content whose catalog row is marked --fix-all-eligible in its consent column (the ranked catalog carries the tier AND consent columns and is authoritative on which scored-group items qualify - see playbooks.md). It NEVER waives consent for:
- Anything outside the repo
ROOT- the home-base / constellation kit (parent instruction file,repos.yaml, run-everything scripts) is always explicit-consent-only. - Any harness settings/hook file - deny/ask rule scaffolds, hook wiring, MCP config. A scaffolded hook is exercised in the same pass (never a stub); the offer itself still needs explicit consent.
- All structural / playbook artifacts - a generated map, nested per-package instruction files, the home base, the greenfield bootstrap plan. Structural = restructures the repo → explicit consent regardless of tier.
- On greenfield,
--fix-allapplies ONLY to exercised hygiene files (.gitignore, lockfile,.env.example,.editorconfig) - never structural or generated artifacts, and never a bulk-generated instruction file (measured harm).
Re-run reuse: a Phase 7 re-assessment reuses the session's Phase 0.5 classification and Phase 0.6 answers; only the affected criteria/gates re-verify. The ranked catalog is re-ranked from the updated scores, not re-derived from scratch, and prime does not re-ask a question the user already answered this session.
Scope Control
- Never create LICENSE files — license choice requires explicit user decision
- Never offer Pillar 6-8 fixes — production readiness is informational only
- Focus fixes on what helps agents work (not team governance)
© gmickel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 11 other files (references) in plugins/flow-next/skills/flow-next-prime of gmickel/flow-next.
- SKILL.md
- classification.md
- harness.md
- pillars.md
- playbooks.md
- references/boot-probe.md
- references/map-suggestion.md
- references/monorepo-sampling.md
- references/remediation-flow.md
- remediation.md
- stacks.md
- workflow.md
Open the folder on GitHubat commit c1ce203
Compare with similar skills
Flow Next Prime 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 |
|---|---|---|---|---|---|---|
| Flow Next Prime this skillgmickel/flow-next | 709 | — | ~2.1k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Setup Matt Pocock Skillsbestofjs/bestofjs | 3.1k | 20 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT |
Similar skills
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.
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.
Setup Matt Pocock Skills
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
More from gmickel/flow-next
All 43 skills in this repoFlow Next Resolve PR
gmickel/flow-next
Resolve PR review feedback. An agent skill from gmickel/flow-next.
Flow Next Resolve PR
gmickel/flow-next
Resolve PR review feedback — fetch unresolved threads, triage, dispatch per-thread resolver agents, validate, commit, reply + resolve via GraphQL.
Flow Next
gmickel/flow-next
Manage .flow/ tasks and specs. An agent skill from gmickel/flow-next.
Flow Next Audit
gmickel/flow-next
Audit .flow/memory/ entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete / Harden per entry.
Flow Next Capture
gmickel/flow-next
Save the current conversation as a source-tagged flow-next spec, then offer review or editing.
Flow Next Chart
gmickel/flow-next
Decision-map discovery for one oversized unclear idea before capture.
Related
Works with
Categories
Questions about Flow Next Prime
What does Flow Next Prime do?
Comprehensive codebase assessment for agent and production readiness. Flow Next Prime is an agent skill from gmickel/flow-next. Comprehensive codebase assessment for agent and production readiness.
When should I use Flow Next Prime?
Flow Next Prime fits situations like: /flow-next:prime.
How do I install Flow Next Prime in Claude Code?
Run `npx skills add gmickel/flow-next --skill flow-next-prime -a claude-code`. Or copy the skill folder (plugins/flow-next/skills/flow-next-prime in gmickel/flow-next) into .claude/skills/flow-next-prime in your project. Claude Code loads it when a task matches its description.
How do I install Flow Next Prime in Codex?
Run `npx skills add gmickel/flow-next --skill flow-next-prime -a codex`. Or copy the skill folder (plugins/flow-next/skills/flow-next-prime in gmickel/flow-next) into .agents/skills/flow-next-prime in your project. Codex loads it when a task matches its description.
Can I use Flow Next Prime 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 gmickel/flow-next --skill flow-next-prime -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flow-next-prime, .gemini/skills/flow-next-prime, .github/skills/flow-next-prime and .opencode/skills/flow-next-prime in your project.
What does Flow Next Prime need to run?
SKILL.md names no scripts, command-line tools or credentials: Flow Next Prime is instructions for the agent only.
Does Flow Next Prime access the network?
SKILL.md names 1 domain. As links in the text: factory.ai. This is read from the text; nothing was executed.
Is Flow Next Prime 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 Flow Next Prime use?
Flow Next Prime 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 Flow Next Prime use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.
What are the alternatives to Flow Next Prime?
Skills that share tags, products or a category with Flow Next Prime: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Flow Next Prime?
gmickel (a GitHub user) maintains it in gmickel/flow-next, which has 709 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 10, 2026.
Source: gmickel/flow-next on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.