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.
Manage git worktrees (create/list/switch/cleanup) and copy .env files.
Install Flow Next Worktree Kit
$ npx skills add gmickel/flow-next --skill flow-next-worktree-kit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gmickel/flow-next flow-next-worktree-kit --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-worktree-kit .claude/skills/flow-next-worktree-kit && 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-worktree-kit" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-worktree-kit into .claude/skills/flow-next-worktree-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-worktree-kit", 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-worktree-kitType 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-worktree-kit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gmickel/flow-next flow-next-worktree-kit --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-worktree-kit .agents/skills/flow-next-worktree-kit && 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-worktree-kit" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-worktree-kit into .agents/skills/flow-next-worktree-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-worktree-kit", 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-worktree-kit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gmickel/flow-next flow-next-worktree-kit --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-worktree-kit .cursor/skills/flow-next-worktree-kit && 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-worktree-kit" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-worktree-kit into .cursor/skills/flow-next-worktree-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-worktree-kit", 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-worktree-kit--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-worktree-kit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gmickel/flow-next flow-next-worktree-kit --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-worktree-kit .gemini/skills/flow-next-worktree-kit && 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-worktree-kit" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-worktree-kit into .gemini/skills/flow-next-worktree-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-worktree-kit", 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-worktree-kitInstalls 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-worktree-kit -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-worktree-kit .github/skills/flow-next-worktree-kit && 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-worktree-kit" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-worktree-kit into .github/skills/flow-next-worktree-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-worktree-kit", 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-worktree-kit -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-worktree-kit --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-worktree-kit .opencode/skills/flow-next-worktree-kit && 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-worktree-kit" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-worktree-kit into .opencode/skills/flow-next-worktree-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-worktree-kit", 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-worktree-kit- GitHub stars
- 709
- Token cost
- ~610 tokens
- SKILL.md length
- 240 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 43
- Repo updated
- First seen
- Licence
- MIT
At a glance
Manage git worktrees (create/list/switch/cleanup) and copy .env files.
- Parallel feature work
- Runs Shell scripts from its folder; calls git and bash
- Isolated review
- Clean workspace
What it does
Flow Next Worktree Kit is an agent skill from gmickel/flow-next. Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
Its SKILL.md is about 610 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/worktree.sh`).
It sits in Development, covering Git worktrees. It works with Git. 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
- Parallel feature work
- Isolated review
- Clean workspace
- User mentions worktrees
Example prompts
- “/flow-next-worktree-kit”
Requirements
- A Bash shell
What it can do on your machine
Read from SKILL.md and the folder at commit 09e291e. 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
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
gitbash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
Flow Next Worktree Kit loads about 610 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 240 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:3
es (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or - NoteMentions a .env fileSKILL.md:28
- `.env*` is copied with no overwrite (symlinks skipped)
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); the scripts in this folder are not scanned.
SKILL.md
The full file from gmickel/flow-next at commit 09e291e, republished under its MIT licence (© gmickel). 240 words, ~610 tokens.
Download SKILL.mdSave it as
.claude/skills/flow-next-worktree-kit/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- flow-next-worktree-kit
- description
- Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
Worktree kit
Use the manager script for all worktree actions.
WORKTREE_SH="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/skills/flow-next-worktree-kit/scripts/worktree.sh"
[ -f "$WORKTREE_SH" ] || WORKTREE_SH="<plugin-root>/skills/flow-next-worktree-kit/scripts/worktree.sh" # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
bash "$WORKTREE_SH" <command> [args]Commands:
create <name> [base]listswitch <name>(prints the worktree path; it cannot change your shell's directory - usecd "$(... switch <name>)")cleanup [<name>...] [--yes](no args = interactive; names skip the prompt;--yesskips the confirmation, required off a terminal)copy-env <name>
Safety notes:
createdoes not change the current branchcreatesets no upstream on the new branch (--no-track) - under the upstream-based push modes (simple,upstream,current) a baregit pushcannot aim at the base branch; under the defaultpush.default=simple(withoutpush.autoSetupRemote) the first push needsgit push -u origin <name>(legacypush.default=matchingpushes all name-matched branches regardless of upstream)cleanupdoes not force-remove worktrees and does not delete branchescleanupdeletes the worktree directory (including ignored files); removal fails if the worktree is not clean.env*is copied with no overwrite (symlinks skipped)- refuses to operate if
.worktrees/or any worktree path component is a symlink copy-envonly targets registered worktreesoriginfetch is optional; local base refs are allowed- fetch from
originonly when base looks like a branch - Worktrees live under
.worktrees/ createinitializes.worktrees/.gitignore(*plus!.gitignore) when absent, sogit add -Acannot stage nested worktrees as gitlinks; existing custom ignore files are preserved
Shared claim state. Parallel agents in sibling worktrees driving flowctl on the same repo share claim state via .git/flow-state. Set FLOW_STATE_DIR per agent (outside the tree) when running flow pipelines concurrently.
© 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 1 other file (scripts) in plugins/flow-next/skills/flow-next-worktree-kit of gmickel/flow-next.
- SKILL.md
- scripts/worktree.sh
Open the folder on GitHubat commit 09e291e
Compare with similar skills
Flow Next Worktree Kit 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 Worktree Kit this skillgmickel/flow-next | 709 | — | ~610 | Automated safety check: Notes | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Finishing A Development Branchfarm-fe/farm | 5.6k | 34 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Git Worktree Cleanuplobehub/lobehub | 83k | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Ccmanager Configkbwo/ccmanager | 1.3k | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
Git Worktree Cleanup
lobehub/lobehub
Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
Ccmanager Config
kbwo/ccmanager
Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json.
Cap Feature Building Workflow
CapSoftware/Cap
Builds a Cap feature in an isolated Git worktree with disposable dev resources, verification, a recorded demo and a neutral pull request, started with /building.
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 Worktree Kit
What does Flow Next Worktree Kit do?
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Flow Next Worktree Kit is an agent skill from gmickel/flow-next.env files.
When should I use Flow Next Worktree Kit?
Flow Next Worktree Kit fits situations like: parallel feature work; isolated review; clean workspace; user mentions worktrees.
How do I install Flow Next Worktree Kit in Claude Code?
Run `npx skills add gmickel/flow-next --skill flow-next-worktree-kit -a claude-code`. Or copy the skill folder (plugins/flow-next/skills/flow-next-worktree-kit in gmickel/flow-next) into .claude/skills/flow-next-worktree-kit in your project. Claude Code loads it when a task matches its description.
How do I install Flow Next Worktree Kit in Codex?
Run `npx skills add gmickel/flow-next --skill flow-next-worktree-kit -a codex`. Or copy the skill folder (plugins/flow-next/skills/flow-next-worktree-kit in gmickel/flow-next) into .agents/skills/flow-next-worktree-kit in your project. Codex loads it when a task matches its description.
Can I use Flow Next Worktree Kit 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-worktree-kit -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-worktree-kit, .gemini/skills/flow-next-worktree-kit, .github/skills/flow-next-worktree-kit and .opencode/skills/flow-next-worktree-kit in your project.
What does Flow Next Worktree Kit need to run?
Going by SKILL.md and its folder, Flow Next Worktree Kit needs a shell for the scripts in its folder and the command-line tools its instructions call (git and bash). Our summary lists: A Bash shell.
Does Flow Next Worktree Kit access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Flow Next Worktree Kit safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Flow Next Worktree Kit use?
Flow Next Worktree Kit 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 Worktree Kit use?
About 610 tokens (SKILL.md is roughly 2.4k 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 Flow Next Worktree Kit?
Skills that share tags, products or a category with Flow Next Worktree Kit: Finishing a Development Branch (obra/superpowers, 297k stars), Finishing A Development Branch (farm-fe/farm, 5.6k stars), Git Worktree Cleanup (lobehub/lobehub, 83k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Flow Next Worktree Kit?
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 7, 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.