agentleFS
hmj1026hmj1026/dhpk/skills/git-worktree/SKILL.md

git-worktree

Skill2 starsChanged 6 days agoMITView on GitHub

Manage Git worktree lifecycle with exact native git targets, branch/path validation, and dirty-worktree safety. Covers adding, listing, removing, and pruning worktrees. Not for: branch merging, broad cleanup, or removing or pruning without confirmation. Output: exact commands plus resulting worktree status.

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-native-architecture, document-review and 7 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.
  • CodeWithBehnamSkill

    agent-native-architecture

    Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.

    Also in 3 projects that use this

  • CodeWithBehnamSkill

    document-review

    This skill should be used to refine brainstorm or plan documents before proceeding to the next workflow step. It applies when a brainstorm or plan document exists and the user wants to improve it.

    Also in 3 projects that use this

  • MicrosoftSkill

    git-commit

    Stage user-selected paths, confirm the exact staged set, and create one local Conventional Commit, or generate a commit message for staged changes without committing. Use when you want a guarded commit or a ready-to-paste message.

    Also in 3 projects that use this

  • MicrosoftSkill

    grill-with-docs

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

    Also in 3 projects that use this

  • OpenAISkill

    brainstorming

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Run from the consumer repository.

    line 16
  2. Very specific:

    Use native Git operations only.

    line 22

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

Git Worktree

Workflow

Run from the consumer repository. Resolve one sub-command and preserve [add|list|remove|prune] [--branch <name>] [--base <ref>]. Inspect git worktree list --porcelain and the current branch first. Resolve every target path and branch explicitly; a missing branch/path or dirty relevant worktree stops the operation.

Use native Git operations only. add uses the repository parent and the wt-{repo-shortname}-{purpose} naming convention, then reports the exact git worktree add command and next steps. list reports each worktree and status. remove and prune preview their exact targets and require explicit confirmation before mutation; never use a force option to bypass a dirty check. The detailed command sequence is in references/workflow.md.

When NOT to Use

  • A merge, rebase, branch deletion, or remote operation is requested.
  • The target worktree is missing, ambiguous, or dirty.
  • Removal or pruning has not received explicit confirmation.

Output

  • add: exact command, created path, branch, and next steps.
  • list: a formatted table derived from native worktree records.
  • remove/prune: confirmation state, exact target/command, and resulting status; no confirmation means NOT_RUN.
  • Missing or dirty targets and native Git failures are terminal failures.

Verification

  • Every target path and branch was resolved before a write.
  • Relevant worktrees were checked with git status --porcelain.
  • Remove/prune has explicit confirmation, or no mutation was attempted.
  • Final git worktree list --porcelain evidence matches the report.

References

  • references/workflow.md — native commands, naming, dirty checks, confirmation, and output details.

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.