using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans.

509 stars

Best use case

using-git-worktrees is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans.

Teams using using-git-worktrees should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/using-git-worktrees/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/methodologies/superpowers/skills/using-git-worktrees/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/using-git-worktrees/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How using-git-worktrees Compares

Feature / Agentusing-git-worktreesStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when starting feature work that needs isolation from current workspace or before executing implementation plans.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Using Git Worktrees

## Overview

Create isolated workspaces sharing the same repository. Systematic directory selection + safety verification.

**Core principle:** Isolated workspace before implementation.

## Process

1. Check existing directories (.worktrees/ or worktrees/)
2. Verify directory is gitignored
3. Create worktree with new branch
4. Run project setup (auto-detect npm/cargo/pip/go)
5. Verify clean test baseline
6. Report ready

## Safety

- Always verify worktree directory is gitignored
- Always run baseline tests
- Report failures before proceeding

## Agents Used

- Process agents referenced in `superpowers-workflow.js`

## Tool Use

Referenced by `executing-plans` and `subagent-driven-development` processes.