npx skills add https://github.com/obra/superpowers --skill using-git-worktreesHow Using Git Worktrees fits into a Paperclip company.
Using Git Worktrees drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.
Pre-configured AI company — 18 agents, 18 skills, one-time purchase.
SKILL.md218 linesExpandCollapse
---name: using-git-worktreesdescription: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification--- # 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. **Announce at start:** "I'm using the using-git-worktrees skill to set up an isolated workspace." ## Directory Selection Process Follow this priority order: ### 1. Check Existing Directories ```bash# Check in priority orderls -d .worktrees 2>/dev/null # Preferred (hidden)ls -d worktrees 2>/dev/null # Alternative``` **If found:** Use that directory. If both exist, `.worktrees` wins. ### 2. Check CLAUDE.md ```bashgrep -i "worktree.*director" CLAUDE.md 2>/dev/null``` **If preference specified:** Use it without asking. ### 3. Ask User If no directory exists and no CLAUDE.md preference: ```No worktree directory found. Where should I create worktrees? 1. .worktrees/ (project-local, hidden)2. ~/.config/superpowers/worktrees/<project-name>/ (global location) Which would you prefer?``` ## Safety Verification ### For Project-Local Directories (.worktrees or worktrees) **MUST verify directory is ignored before creating worktree:** ```bash# Check if directory is ignored (respects local, global, and system gitignore)git check-ignore -q .worktrees 2>/dev/null || git check-ignore -q worktrees 2>/dev/null``` **If NOT ignored:** Per Jesse's rule "Fix broken things immediately":1. Add appropriate line to .gitignore2. Commit the change3. Proceed with worktree creation **Why critical:** Prevents accidentally committing worktree contents to repository. ### For Global Directory (~/.config/superpowers/worktrees) No .gitignore verification needed - outside project entirely. ## Creation Steps ### 1. Detect Project Name ```bashproject=$(basename "$(git rev-parse --show-toplevel)")``` ### 2. Create Worktree ```bash# Determine full pathcase $LOCATION in .worktrees|worktrees) path="$LOCATION/$BRANCH_NAME" ;; ~/.config/superpowers/worktrees/*) path="~/.config/superpowers/worktrees/$project/$BRANCH_NAME" ;;esac # Create worktree with new branchgit worktree add "$path" -b "$BRANCH_NAME"cd "$path"``` ### 3. Run Project Setup Auto-detect and run appropriate setup: ```bash# Node.jsif [ -f package.json ]; then npm install; fi # Rustif [ -f Cargo.toml ]; then cargo build; fi # Pythonif [ -f requirements.txt ]; then pip install -r requirements.txt; fiif [ -f pyproject.toml ]; then poetry install; fi # Goif [ -f go.mod ]; then go mod download; fi``` ### 4. Verify Clean Baseline Run tests to ensure worktree starts clean: ```bash# Examples - use project-appropriate commandnpm testcargo testpytestgo test ./...``` **If tests fail:** Report failures, ask whether to proceed or investigate. **If tests pass:** Report ready. ### 5. Report Location ```Worktree ready at <full-path>Tests passing (<N> tests, 0 failures)Ready to implement <feature-name>``` ## Quick Reference | Situation | Action ||-----------|--------|| `.worktrees/` exists | Use it (verify ignored) || `worktrees/` exists | Use it (verify ignored) || Both exist | Use `.worktrees/` || Neither exists | Check CLAUDE.md → Ask user || Directory not ignored | Add to .gitignore + commit || Tests fail during baseline | Report failures + ask || No package.json/Cargo.toml | Skip dependency install | ## Common Mistakes ### Skipping ignore verification - **Problem:** Worktree contents get tracked, pollute git status- **Fix:** Always use `git check-ignore` before creating project-local worktree ### Assuming directory location - **Problem:** Creates inconsistency, violates project conventions- **Fix:** Follow priority: existing > CLAUDE.md > ask ### Proceeding with failing tests - **Problem:** Can't distinguish new bugs from pre-existing issues- **Fix:** Report failures, get explicit permission to proceed ### Hardcoding setup commands - **Problem:** Breaks on projects using different tools- **Fix:** Auto-detect from project files (package.json, etc.) ## Example Workflow ```You: I'm using the using-git-worktrees skill to set up an isolated workspace. [Check .worktrees/ - exists][Verify ignored - git check-ignore confirms .worktrees/ is ignored][Create worktree: git worktree add .worktrees/auth -b feature/auth][Run npm install][Run npm test - 47 passing] Worktree ready at /Users/jesse/myproject/.worktrees/authTests passing (47 tests, 0 failures)Ready to implement auth feature``` ## Red Flags **Never:**- Create worktree without verifying it's ignored (project-local)- Skip baseline test verification- Proceed with failing tests without asking- Assume directory location when ambiguous- Skip CLAUDE.md check **Always:**- Follow directory priority: existing > CLAUDE.md > ask- Verify directory is ignored for project-local- Auto-detect and run project setup- Verify clean test baseline ## Integration **Called by:**- **brainstorming** (Phase 4) - REQUIRED when design is approved and implementation follows- **subagent-driven-development** - REQUIRED before executing any tasks- **executing-plans** - REQUIRED before executing any tasks- Any skill needing isolated workspace **Pairs with:**- **finishing-a-development-branch** - REQUIRED for cleanup after work completeBrainstorming
Forces Claude to actually think before coding, which frankly should be the default but isn't. Blocks all implementation until you've walked through context expl
Dispatching Parallel Agents
When you've got multiple independent failures across different test files or subsystems, this cuts debugging time by running separate agents in parallel instead
Executing Plans
Takes a written implementation plan and executes it step by step with proper checkpoints. Loads the plan file, reviews it critically for gaps or unclear instruc