Install the "superpowers-using-git-worktrees" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-using-git-worktrees into .claude/skills/superpowers-using-git-worktrees/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-using-git-worktrees", 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 christopherarter/superpowers-reasonix --skill superpowers-using-git-worktrees -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "superpowers-using-git-worktrees" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-using-git-worktrees into .agents/skills/superpowers-using-git-worktrees/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-using-git-worktrees", 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 christopherarter/superpowers-reasonix --skill superpowers-using-git-worktrees -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "superpowers-using-git-worktrees" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-using-git-worktrees into .cursor/skills/superpowers-using-git-worktrees/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-using-git-worktrees", 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 christopherarter/superpowers-reasonix --skill superpowers-using-git-worktrees -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "superpowers-using-git-worktrees" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-using-git-worktrees into .gemini/skills/superpowers-using-git-worktrees/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-using-git-worktrees", 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.
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 christopherarter/superpowers-reasonix --skill superpowers-using-git-worktrees -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "superpowers-using-git-worktrees" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-using-git-worktrees into .github/skills/superpowers-using-git-worktrees/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-using-git-worktrees", 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 christopherarter/superpowers-reasonix --skill superpowers-using-git-worktrees -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "superpowers-using-git-worktrees" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-using-git-worktrees into .opencode/skills/superpowers-using-git-worktrees/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-using-git-worktrees", 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
superpowers-using-git-worktrees
GitHub stars
102
Token cost
~1.4k tokens
SKILL.md length
576 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT
At a glance
Feature work needing an isolated workspace, or executing a plan?
Works in 4 steps: Detect Existing Isolation → Create Isolated Workspace → Project Setup → …
Tasks that involve Git worktrees
SKILL.md covers Overview, Step 0: Detect Existing…, Step 1: Create Isolated… and Step 3: Project Setup, plus 3 more sections
Calls git, npm and cargo
What it does
Superpowers Using Git Worktrees is an agent skill from christopherarter/superpowers-reasonix. Feature work needing an isolated workspace, or executing a plan? Load first.
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, covering Git worktrees. It works with Git. The repository describes itself as: Superpowers skill port to Reasonix coding harness. The licence is MIT.
When your agent uses it
Tasks that involve Git worktrees
Example prompts
“/superpowers-using-git-worktrees”
Requirements
Python 3
Node.js
Workflow steps
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d202ba4. 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
npm
cargo
go
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 npm, 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
Superpowers Using Git Worktrees loads about 1.4k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 576 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~27
When it runs· the whole SKILL.md, loaded when a task matches
~1.4k
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.
Submodule guard:GIT_DIR != GIT_COMMON also true inside submodules. Verify not a submodule before concluding "worktree":
bash
# If this returns a path, you're in a submodule, not a worktree — treat as normal repo
git rev-parse --show-superproject-working-tree 2>/dev/null
If GIT_DIR != GIT_COMMON (and not a submodule): Already in linked worktree. Skip to Step 3, do NOT create another. Report branch state:
On a branch: "Already in isolated workspace at <path> on branch <name>."
Detached HEAD: "Already in isolated workspace at <path> (detached HEAD, externally managed). Branch creation needed at finish."
If GIT_DIR == GIT_COMMON (or in a submodule): Normal repo checkout. Preference declared? Honor it, no asking. Else ask consent:
"Would you like me to set up an isolated worktree? It protects your current branch from changes."
Declines: work in place, skip to Step 3 — do NOT start editing feature code on the current branch first.
Step 1: Create Isolated Workspace
1a. Native Worktree Tools (preferred)
Already have a worktree mechanism — a tool named EnterWorktree, WorktreeCreate, a /worktree command, or a --worktree flag? Use it, skip to Step 3.
Native tools handle placement, branch creation, cleanup. Using git worktree add when a native tool exists creates phantom state the harness can't manage. No native tool: proceed to Step 1b.
1b. Git Worktree Fallback
Only use if Step 1a does not apply. Explicit user preference always beats filesystem state.
Directory Selection
Check instructions for declared directory preference. Use it, no asking.
Check for existing project-local worktree directory:bash
ls -d .worktrees 2>/dev/null # Preferred (hidden)
ls -d worktrees 2>/dev/null # Alternative
Both exist? .worktrees wins.
Check for existing global directory:bash
project=$(basename "$(git rev-parse --show-toplevel)")
ls -d ~/.config/reasonix/worktrees/$project 2>/dev/null
No other guidance: default to .worktrees/ at project root.
If NOT ignored: add to .gitignore, commit, proceed. Why critical: prevents committing worktree contents. Global directories need no verification.
Show full SKILL.md (239 more words)Show less
Create the Worktree
bash
# For project-local: path="$LOCATION/$BRANCH_NAME"
# For global: path="~/.config/reasonix/worktrees/$project/$BRANCH_NAME"
git worktree add "$path" -b "$BRANCH_NAME"
cd "$path"
Sandbox fallback:git worktree add fails with permission error (sandbox denial — Reasonix confines writes to [sandbox] workspace_root)? Tell the user the sandbox blocked it, working in the current directory instead. Run setup and baseline tests in place.
Step 3: Project Setup
Auto-detect and run setup, bash:
bash
if [ -f package.json ]; then npm install; fi
if [ -f Cargo.toml ]; then cargo build; fi
if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
if [ -f pyproject.toml ]; then poetry install; fi
if [ -f go.mod ]; then go mod download; fi
Step 4: Verify Clean Baseline
Run tests, ensure clean baseline (npm test / cargo test / pytest / go test ./...).
Tests fail: report failures, ask whether to proceed or investigate. Pass: report ready.
Worktree ready at <full-path>
Tests passing (<N> tests, 0 failures)
Ready to implement <feature-name>
Quick Reference
Situation
Action
Already in linked worktree
Skip creation (Step 0)
In a submodule
Treat as normal repo (Step 0 guard)
Native worktree tool available
Use it (Step 1a)
No native tool
Git worktree fallback (Step 1b)
.worktrees/ exists
Use it (verify ignored)
Both .worktrees/ and worktrees/ exist
Use .worktrees/
Neither exists
Check instruction file, then default .worktrees/
Directory not ignored
Add to .gitignore + commit
Permission error on create
Sandbox fallback, work in place
Tests fail during baseline
Report failures + ask
Red Flags
Never:
Create a worktree when Step 0 detects existing isolation
Use git worktree add when a native worktree tool exists — #1 mistake
Skip Step 1a, jump straight to git commands
Create project-local worktree without verifying it's ignored
Skip baseline test verification
Proceed with failing tests without asking
Always: run Step 0 first; prefer native tools; follow directory priority (existing > global legacy > instruction file > default); verify ignored for project-local; auto-detect and run setup; verify clean test baseline.
Superpowers Using Git Worktrees 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.
Superpowers Using Git Worktrees compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Superpowers Using Git Worktrees this skillchristopherarter/superpowers-reasonix
Build PX4 board firmware on macOS in the px4-dev Docker container, including git worktrees, and stage commit-labeled artifacts without flashing hardware.
Creates or reuses an isolated AgentsMesh Git worktree from a verified base branch, preserves existing changes, and optionally starts the worktree-scoped development environment.
Sets up an isolated workspace before feature work or plan execution, preferring native worktree tools and falling back to git worktree, with instructions in Chinese.
Feature work needing an isolated workspace, or executing a plan? Superpowers Using Git Worktrees is an agent skill from christopherarter/superpowers-reasonix. Feature work needing an isolated workspace, or executing a plan?
When should I use Superpowers Using Git Worktrees?
Superpowers Using Git Worktrees fits situations like: tasks that involve Git worktrees.
How do I install Superpowers Using Git Worktrees in Claude Code?
Run `npx skills add christopherarter/superpowers-reasonix --skill superpowers-using-git-worktrees -a claude-code`. Or copy the skill folder (skills/superpowers-using-git-worktrees in christopherarter/superpowers-reasonix) into .claude/skills/superpowers-using-git-worktrees in your project. Claude Code loads it when a task matches its description.
How do I install Superpowers Using Git Worktrees in Codex?
Run `npx skills add christopherarter/superpowers-reasonix --skill superpowers-using-git-worktrees -a codex`. Or copy the skill folder (skills/superpowers-using-git-worktrees in christopherarter/superpowers-reasonix) into .agents/skills/superpowers-using-git-worktrees in your project. Codex loads it when a task matches its description.
Can I use Superpowers Using Git Worktrees 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 christopherarter/superpowers-reasonix --skill superpowers-using-git-worktrees -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/superpowers-using-git-worktrees, .gemini/skills/superpowers-using-git-worktrees, .github/skills/superpowers-using-git-worktrees and .opencode/skills/superpowers-using-git-worktrees in your project.
What does Superpowers Using Git Worktrees need to run?
Going by SKILL.md and its folder, Superpowers Using Git Worktrees needs the command-line tools its instructions call (git, npm, cargo and go). Our summary lists: Python 3; Node.js.
Does Superpowers Using Git Worktrees access the network?
SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Superpowers Using Git Worktrees 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 Superpowers Using Git Worktrees use?
Superpowers Using Git Worktrees 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 Superpowers Using Git Worktrees 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 Superpowers Using Git Worktrees?
Skills that share tags, products or a category with Superpowers Using Git Worktrees: Build Px4 macOS (PX4/PX4-Autopilot, 13k stars), Worktree (AgentsMesh/AgentsMesh, 2.4k stars), Git Worktree Isolation (jnMetaCode/superpowers-zh, 8.3k stars) and Cursor Composer Task Delegate (Chachamaru127/claude-code-harness, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Superpowers Using Git Worktrees?
christopherarter (a GitHub user) maintains it in christopherarter/superpowers-reasonix, which has 102 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 20, 2026.
