agentleFS
AtilaMedeirosAtilaMedeiros/skills/using-git-worktrees/SKILL.md

using-git-worktrees

Skill1 starsChanged 9 months agoNo licenceView on GitHub

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

  • Installs packages

192 other projects use a version of this, 148 of them edited; 95 of 141 edited versions we compared changed its rules; 7 new projects in the last 4 weeks, against 14 the 4 before.

How people change it

95 of 141 edited versions changed its rules, and some changes recur.

Of the 141 edited versions we compared: 45 keep every rule, 1 is an older text, 95 made changes of their own.

Not in older versions

  1. Run tests to ensure worktree starts clean:missing from 1 of 1
  2. Fix: Always use git check-ignore before creating project-local worktreemissing from 1 of 1
  3. Fix: Follow priority: existing > CLAUDE.md > askmissing from 1 of 1

Rules people drop

  1. If no directory exists and no CLAUDE.md preference:dropped by 81 of 95
  2. Add appropriate line to .gitignoredropped by 81 of 95
  3. Follow this priority order:dropped by 79 of 95
  4. If preference specified: Use it without asking.dropped by 79 of 95
  5. Fix: Follow priority: existing > CLAUDE.md > askdropped by 79 of 95
  6. Follow directory priority: existing > CLAUDE.md > askdropped by 79 of 95
  7. Create worktree without verifying it's ignored (project-local)dropped by 70 of 95
  8. Verify directory is ignored for project-localdropped by 70 of 95

Rules people add

  1. Ensure work happens in an isolated workspace. Prefer your platform's native worktree tools. Fall back to manual git worktrees only when no native tool is available.added by 68 of 95
  2. If NOT ignored: Add to .gitignore, commit the change, then proceed.added by 67 of 95
  3. Sandbox fallback: If git worktree add fails with a permission error (sandbox denial), tell the user the sandbox blocked worktree creation and you're working in the current directory instead. Then run setup and baseline tests in place.added by 67 of 95
  4. Only proceed to Step 1b if you have no native worktree tool available.added by 66 of 95
  5. Follow this priority order. Explicit user preference always beats observed filesystem state.added by 66 of 95
  6. Create a worktree when Step 0 detects existing isolationadded by 19 of 95
  7. Run Step 0 detection firstadded by 19 of 95
  8. Fix: Always run Step 0 before creating anythingadded by 18 of 95

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 7 new projects took it in the last 4 weeks, 0.5× the 4 weeks before.

Week of Sep 20: 1 new projectWeek of Sep 27: 4 new projectsWeek of Oct 4: 5 new projectsWeek of Oct 11: 4 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 3 new projectsWeek of Nov 1: 3 new projectsWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 20 projects that use this

  • frankxaiSkill

    defense-in-depth

    Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible

    Also in 4 projects that use this

  • kntismSkill

    condition-based-waiting

    Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

    Also in 3 projects that use this

  • MicrosoftSkill

    root-cause-tracing

    Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

    Also in 4 projects that use this

  • +3 more from Leodorareluctant259

The file

We split this skill into the rules it gives an agent

12 rules. 1 is common, 10 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 168 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 168 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.

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.