Skip to content
mcp/skillhub

Agent Skill

Using Git Worktrees skill

using-git-worktreesSuperpowersskills/using-git-worktrees/SKILL.md

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

303kMIT

always on

36 tokname + description

once used

1,580 tokSKILL.md body

bundled files

0

installs

215kskills.sh

Install the Using Git Worktrees skill

Skills CLI (Claude Code, Codex, Cursor and others)

npx skills add https://github.com/obra/superpowers --skill using-git-worktrees

Claude Code, by hand (all projects)

git clone --depth 1 https://github.com/obra/superpowers.git /tmp/superpowers
mkdir -p ~/.claude/skills
cp -R /tmp/superpowers/skills/using-git-worktrees ~/.claude/skills/using-git-worktrees

For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.

What it costs your context

Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.

WhenWhat loadsCost
Every sessionName and description36 tok
When the agent uses itThe SKILL.md instructions1,580 tok
Only if openedNo bundled files—

Until it is used, using-git-worktrees costs about 38× less than the median MCP server we measured (1,362 tokens on every turn). Installing all 15 skills from obra/superpowers would load 489 tokens of descriptions. Skills vs MCP study

Checks

Our checks found nothing to flag: it follows the Agent Skills specification's naming and size guidelines and doesn't pipe downloads into a shell.

Checked 2026-10-22 · method

What's inside

The headings of its SKILL.md. Read the full file on GitHub.

  • Using Git Worktrees
  • Overview
  • Step 0: Detect Existing Isolation
  • Step 1: Create Isolated Workspace
  • 1a. Native Worktree Tools (preferred)
  • 1b. Git Worktree Fallback
  • Step 2: Project Setup
  • Step 3: Verify Clean Baseline
  • Report
  • Quick Reference
  • Common Rationalizations

More skills from obra/superpowers

All skills in this repo
  1. brainstormingobra/superpowers

    You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

    401k446 tok idle · 3,062 in use
  2. systematic-debuggingobra/superpowers

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    303k221 tok idle · 2,175 in use
  3. writing-plansobra/superpowers

    Use when you have a spec or requirements for a multi-step task, before touching code

    281k21 tok idle · 2,284 in use
  4. using-superpowersobra/superpowers

    Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

    269k28 tok idle · 700 in use
  5. requesting-code-reviewobra/superpowers

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    260k22 tok idle · 660 in use
  6. test-driven-developmentobra/superpowers

    Use when implementing any feature or bugfix, before writing implementation code

    257k17 tok idle · 2,316 in use
  7. Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

    249k43 tok idle · 803 in use
  8. executing-plansobra/superpowers

    Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

    241k35 tok idle · 4,228 in use