Skip to content
SkillModel-led1,575 tokens in use

using-git-worktrees

Creates an isolated git workspace for feature work, using your harness's native tool first and git worktree as a fallback.

322,762 stars on the repository MIT Licenseobra/superpowers · skills/using-git-worktrees
/plugin install superpowers@claude-plugins-official
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing using-git-worktrees costs

35tokens idle
1,575tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectednetworkdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples9/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 21
  • Reaches the network−10

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 108

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity56
  • Maintenance68
  • Community64
  • Maturity36
  • Momentum40

Using Git Worktrees ensures work happens in an isolated workspace. It first checks whether you are already in a linked worktree, guarding against submodules, then asks for consent, then prefers a native worktree tool and falls back to git worktree add. It verifies the directory is ignored, installs dependencies and runs the tests for a clean baseline.

What You Get

  • Detection of linked worktrees and submodules by comparing git directories
  • A directory choice order: your instruction, an existing .worktrees or worktrees folder, then .worktrees
  • A check that the worktree folder is git-ignored, with a .gitignore commit if it is not
  • Automatic dependency setup for Node, Rust, Python and Go projects
  • A baseline test run and a short ready report

Common Use Cases

  • Starting a feature without touching your current branch
  • Preparing a clean workspace before executing an implementation plan
  • Working in place when a sandbox blocks worktree creation

What Makes It Unique

It puts the harness first: a native tool such as EnterWorktree handles placement and cleanup, and raw git worktree add is the fallback. It also treats consent, submodule false positives and unignored directories as explicit steps.

Under The Hood

Instructions with shell snippets. The agent runs git rev-parse, check-ignore, branch and worktree add, may edit .gitignore and commit it, runs a dependency install such as npm install, cargo build, pip install, poetry install or go mod download depending on the project files, and then runs the test suite. Installs reach package registries.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers