agentleFS
Sign inStart free
bostonaholicbostonaholic/team/skills/team-worktree/SKILL.md

team-worktree

Skill11 starsChanged 3 months agoMITView on GitHub

Use for isolated worktrees only on explicit request. Never infer from work needing isolation. Applies project conventions.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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. Distinctive:

    Before finalizing prose you author, read the writing standards.

    line 10
  2. Very specific:

    Create one isolated git worktree per involved repo, all on branch <id>, without touching any main working tree: the home repo in …

    line 12
  3. Distinctive:

    Read each reference completely when reaching it, in order.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Team Worktree

Before finalizing prose you author, read the writing standards.

Create one isolated git worktree per involved repo, all on branch <id>, without touching any main working tree: the home repo in single-repo mode (default), or every repo in docs/plans/<id>/4-repos.md when it exists.

Core contracts

  • Detect a linked checkout with git rev-parse --git-dir and git rev-parse --git-common-dir.
  • Non-default branch in an existing linked checkout → skip worktree creation for this repo.
  • Default branch → report and stop.
  • Single-repo: git worktree add .claude/worktrees/<branch>. Each 4-repos.md entry: git -C <repo> worktree add .claude/worktrees/<branch>.
  • Record every created path under ## Worktrees in 4-repos.md.

Procedure references

Read each reference completely when reaching it, in order; later stages depend on earlier state and gates.

  1. Input
  2. Detect mode
  3. Detect existing worktree
  4. Execution

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