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.
Create a Codex-gated spec issue from a triaged report, concept, or idea
$ npx skills add gittower/git-flow-next --skill create-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gittower/git-flow-next create-spec --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/gittower/git-flow-next.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-spec .claude/skills/create-spec && 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 "create-spec" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/create-spec into .claude/skills/create-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-spec", 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/gittower/git-flow-next/tree/main/.claude/skills/create-specType 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 gittower/git-flow-next --skill create-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gittower/git-flow-next create-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/create-spec .agents/skills/create-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-spec" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/create-spec into .agents/skills/create-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-spec", 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 gittower/git-flow-next --skill create-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gittower/git-flow-next create-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/create-spec .cursor/skills/create-spec && 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 "create-spec" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/create-spec into .cursor/skills/create-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-spec", 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/gittower/git-flow-next.git --path .claude/skills/create-spec--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 gittower/git-flow-next --skill create-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gittower/git-flow-next create-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/create-spec .gemini/skills/create-spec && 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 "create-spec" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/create-spec into .gemini/skills/create-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-spec", 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 gittower/git-flow-next create-specInstalls 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 gittower/git-flow-next --skill create-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/create-spec .github/skills/create-spec && 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 "create-spec" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/create-spec into .github/skills/create-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-spec", 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 gittower/git-flow-next --skill create-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gittower/git-flow-next create-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/create-spec .opencode/skills/create-spec && 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 "create-spec" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/create-spec into .opencode/skills/create-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-spec", 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.
create-specCreate a Codex-gated spec issue from a triaged report, concept, or idea
Create Spec is an agent skill from gittower/git-flow-next. Create a Codex-gated spec issue from a triaged report, concept, or idea
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 sits in Development. It works with GitHub. The repository describes itself as: A modern reimplementation of git-flow in Go that offers greater flexibility while maintaining backward compatibility with the original git-flow and git-flow-avh.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 00d1b4b. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobWriteBashAgentmcp__github__get_issuemcp__github__search_issuesmcp__github__create_issuemcp__github__update_issue…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Create Spec loads about 1.4k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 694 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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Grep, Glob, Write, Bash, Agent, mcp__github__get_issue, mcp__github__search_issues, mcp__githuAutomated 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.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 694 words (~1,395 tokens).
“Turn an accepted bug report, feature request, concept, or idea into an implementation-ready spec issue per the Spec Issues section of ISSUE_GUIDELINES.md. The spec is drafted locally, reviewed by Codex, and only posted to GitHub after user acceptance. The spec…”
Just SKILL.md in .claude/skills/create-spec of gittower/git-flow-next.
Open the folder on GitHubat commit 00d1b4b
Create Spec 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 |
|---|---|---|---|---|---|---|
| Create Spec this skillgittower/git-flow-next | 458 | — | ~1.4k | Automated safety check: Notes | Custom licence | |
| 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 |
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
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.
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.
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
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.
gittower/git-flow-next
Analyzes a GitHub issue for the git-flow-next project and writes an analysis document under .ai/ that covers the affected code and proposes TODO comments.
gittower/git-flow-next
Fetches review comments on a pull request, judges each one, writes the evaluation to a plan file and implements accepted changes, waiting for approval before anything public.
gittower/git-flow-next
Scans open pull requests against the project's review response window and reports which ones need action, read-only unless you approve a reminder.
gittower/git-flow-next
Reviews local commits, branch diffs or pull requests against project guidelines and writes the result to local files, never posting it to GitHub.
gittower/git-flow-next
Creates a commit that follows the project's COMMIT_GUIDELINES.md, choosing the type by what the change does and verifying the result.
gittower/git-flow-next
Builds a two-phase implementation plan from a spec issue, analysis or concept, writing a detailed test plan first and the implementation outline second.
Works with
Categories
Create a Codex-gated spec issue from a triaged report, concept, or idea. Create Spec is an agent skill from gittower/git-flow-next.
Create Spec fits situations like: development work in your project.
Run `npx skills add gittower/git-flow-next --skill create-spec -a claude-code`. Or copy the skill folder (.claude/skills/create-spec in gittower/git-flow-next) into .claude/skills/create-spec in your project. Claude Code loads it when a task matches its description.
Run `npx skills add gittower/git-flow-next --skill create-spec -a codex`. Or copy the skill folder (.claude/skills/create-spec in gittower/git-flow-next) into .agents/skills/create-spec in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gittower/git-flow-next --skill create-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-spec, .gemini/skills/create-spec, .github/skills/create-spec and .opencode/skills/create-spec in your project.
SKILL.md names no scripts, command-line tools or credentials: Create Spec is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Write, Bash, Agent, mcp__github__get_issue, mcp__github__search_issues, mcp__github__create_issue, mcp__github__update_issue, mcp__github__add_issue_comment.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Create Spec has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Create Spec: 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.
gittower (a GitHub organization) maintains it in gittower/git-flow-next, which has 458 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on September 8, 2026.
Source: gittower/git-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.