agentleFS
Sign inStart free
TheBeardedBearSASTheBeardedBearSAS/claude-craft/.claude/skills/parallel-worktrees/SKILL.md

parallel-worktrees

Skill108 starsChanged 17 days agoMITView on GitHub

Parallel git worktrees for concurrent Claude Code sessions. Use when working on multiple features or writer/reviewer workflows.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Remove completed worktrees: git worktree remove ../feature-name

    line 37
  2. Distinctive:

    Never share sessions between worktrees

    line 38

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Parallel Worktrees

Productivity pattern for running multiple Claude Code sessions on the same repository.

See ../../rules/12-context-management.md for detailed documentation.

Quick Reference

Setup

# Create worktree for a feature branch
git worktree add ../feature-name feature/branch-name

# Launch Claude in the worktree
cd ../feature-name && claude

Writer/Reviewer Pattern

TerminalRoleCommand
Terminal 1Writercd ../feature-auth && claude "Implement feature"
Terminal 2Reviewercd ../review-auth && claude "Review the code"

Best Practices

  • 3-5 worktrees maximum
  • One worktree = one task
  • Remove completed worktrees: git worktree remove ../feature-name
  • Never share sessions between worktrees

Cleanup

# List all worktrees
git worktree list

# Remove a worktree
git worktree remove ../feature-name

# Prune stale worktree entries
git worktree prune

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free