agentleFS
Sign inStart free
arumaekawaarumaekawa/codex-skills/skills/manage-git-worktrees/SKILL.md

manage-git-worktrees

Skill4 starsChanged 4 months agoMITView on GitHub

Create, reuse, inspect, and remove Git worktrees with gwq. Use whenever a task requires a separate working directory for branch work or any Git worktree operation, before choosing a worktree path or creation method.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use feat-am/<name> or fix-am/<name> unless otherwise specified.

    line 19
  2. Very specific:

    Never use HEAD as the branch name or create a detached worktree.

    line 21
  3. Distinctive:

    Check the target and uncommitted changes before removal:

    line 34

≈ “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

Manage Git Worktrees

  • Inspect the target repository's worktrees with gwq list and their state with gwq status --no-fetch.
  • Reuse a worktree for the intended branch when available.

Create

Confirm the repository and intended starting HEAD, then run:

gwq add -b WORK_BRANCH
  • Use feat-am/<name> or fix-am/<name> unless otherwise specified.
  • For an existing branch, omit -b.
  • Never use HEAD as the branch name or create a detached worktree.
  • Omit the path argument; let gwq determine the layout. Do not use other worktree creation methods.
  • Confirm the resulting path and branch, and run subsequent commands there.

For a different base:

git branch --no-track WORK_BRANCH BASE
gwq add WORK_BRANCH

Remove

Check the target and uncommitted changes before removal:

gwq remove --dry-run PATTERN
gwq remove PATTERN

Preserve the branch unless deletion is intended (-b). Do not force removal of uncommitted work without explicit user authorization.

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