agentleFS
ArangoGutierrezArangoGutierrez/claude-toolkit/.claude/skills/worktree-guide/SKILL.md

worktree-guide

Skill4 starsChanged 3 months agoMITView on GitHub

Use when creating worktrees or starting implementation work in isolated branches from agents-workbench

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Cleanup: after merge: git worktree remove .worktrees/<name>

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

agents-workbench Worktree Workflow

Branches

  • agents-workbench — local-only coordination hub; do not push it (prevent-push-workbench.sh enforces). Source code is read-only on this branch.
  • Feature branches — created in .worktrees/ from the remote default branch

Worktree Creation (critical)

Branch from the remote ref — local main/master/develop may be stale.

# Detect the right remote (upstream for forks, origin otherwise)
git fetch upstream 2>/dev/null && BASE="upstream/$(git symbolic-ref refs/remotes/upstream/HEAD 2>/dev/null | sed 's@^refs/remotes/upstream/@@' || echo main)" || { git fetch origin && BASE="origin/$(git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@')"; }
git worktree add .worktrees/<name> -b <branch> "$BASE"

Flow

  1. Plan on agents-workbench (AGENTS.md, .agents/plans/)
  2. Create worktree from remote ref (see command above)
  3. Implement in worktree (TDD: Red → Green → Refactor)
  4. Push feature branch, create PR
  5. Cleanup after merge: git worktree remove .worktrees/<name>

Enforcement

  • enforce-worktree.sh hook blocks source code writes on agents-workbench
  • Allowed files on agents-workbench: AGENTS.md, .agents/, .worktrees/, docs/plans/, CLAUDE.md, .cursor/rules/, .gitignore
  • prevent-push-workbench.sh hook blocks pushing agents-workbench to any remote

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.