git-worktrees

name	git-worktrees
description	Use when starting feature work that needs isolation from current workspace — creates isolated git worktrees with safety verification
argument-hint	<branch-name or feature description>
allowed-tools	["Bash","Read"]

Using Git Worktrees

Overview

Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.

Core principle: Systematic directory selection + safety verification = reliable isolation.

When NOT to use this skill manually: The myrmidon-swarm skill owns worktree creation for its background subagents. Use this skill for manual development work, not to duplicate swarm setup.

Directory Selection

Follow this priority order:

1. Check Existing Directories

The tested scripts/prepare_worktree.py helper checks .worktrees and then worktrees. If both exist, .worktrees wins.

2. Check repository guidance

Read AGENTS.md and its referenced repository guidance. If a preference is specified, pass it to the helper with --directory DIRECTORY.

3. Portable default

When no repository preference exists, use the host's temporary directory from tempfile.gettempdir() with <project>-<branch>. This is commonly /tmp on Unix-like hosts and avoids polluting the project directory.

The helper computes the project name from the repository root.

Safety Verification

For Project-Local Directories (.worktrees or worktrees)

MUST verify directory is ignored before creating worktree. The helper fails closed when its project-local directory is not ignored.

If NOT ignored:

1. Add .worktrees/ to .gitignore
2. Commit the change
3. Then proceed with worktree creation

Why critical: Prevents accidentally committing worktree contents to repository.

For /tmp Locations

No .gitignore verification needed — outside the project entirely.

Creation Steps

1. Resolve and record the intended base commit SHA.
2. Keep the target repository as the current working directory. Resolve scripts/prepare_worktree.py against this installed skill directory and invoke that absolute helper path with BRANCH_NAME --start-point BASE_SHA --dry-run. For a contract requiring a distinct branch and path, also pass exact --path and --path-root values.
3. Create it with the same arguments without --dry-run, optionally supplying the documented repository preference through --directory. Never replace the recorded SHA with ambient HEAD.
4. Change to the returned path and run the repository-defined bootstrap when one exists.
5. Verify a clean baseline with the repository-defined tests and report the path, start SHA, and result.

If tests fail: Report failures, ask whether to proceed or investigate.

If tests pass: Report ready.

Cleanup

When work is done, invoke tidy for branch inspection and rebasing. Use the separately approved audit and removal flow in tidy (Phase 1) for worktrees; do not improvise deletion commands.

Preserve the worktree by default. Delivery, merge, abandonment, or a general cleanup request does not authorize removal; tidy must re-audit it and obtain per-path Gate C approval.

Quick Reference

Situation	Action
.worktrees/ exists + ignored	Use it
Neither exists	Use the host temporary directory with <project>-<branch>
Directory not ignored	Add to .gitignore + commit first
Tests fail at baseline	Report failures + ask before proceeding

Common Mistakes

• Skipping ignore verification for project-local worktrees → contents get tracked
• Proceeding with failing baseline → can't distinguish new bugs from pre-existing
• Not cleaning up → stale worktrees accumulate

Integration

Pairs with:

• Invoke tidy for worktree audit and removal (its first phase) and branch inspection.
• Verify with fresh runnable evidence per the evidence-integrity policy before finishing and cleaning up.

---

Adapted from obra/superpowers under the MIT License. Copyright (c) 2025 Jesse Vincent.