Using Git Worktrees

Using Git Worktrees is a DevOps skill for Claude Code, published by GanyuanRan in Aegis.

1.1K stars50 forkson GanyuanRan/AegisAdded 2026/08/21+2% in starsRepository updated 2026/08/19

agent-skillsai-agentsai-codingarchitecture-driven-developmentawsome-coding-pluginbaseline-firstclaude-codecodexcoding-agentsdivedsh-pluginevidence-drivenfirst-principlesopencodesoftware-architecturespec-driven-developmentspec-kit

Install in seconds

Install Using Git Worktrees

Copy Using Git Worktrees into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/GanyuanRan/Aegis/tree/main/skills/using-git-worktrees ~/.claude/skills/using-git-worktrees

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/GanyuanRan/Aegis.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/using-git-worktrees/SKILL.md in GanyuanRan/Aegis
Installs to: ~/.claude/skills/using-git-worktrees
Collection: One of 22 skills cataloged from this repository
Category: DevOps — 798 skills

What Using Git Worktrees does

Using Git Worktrees helps when a task needs a separate checkout, dirty state blocks branch switching, or the repository explicitly requires a worktree. It guides safe creation, placement, setup, and cleanup of task-owned worktrees.

Using Git Worktrees is cataloged under DevOps on DirSkills. Using Git Worktrees comes from a repository tagged agent-skills, ai-agents, ai-coding, architecture-driven-development and awsome-coding-plugin.

Documentation

README

Excerpt

Using Git Worktrees

Overview

A worktree is an exception for simultaneously checking out another Git history, not a general safety badge. Prefer the current workspace and reuse an existing suitable worktree. A branch decision and a worktree decision are separate.

Core principle: create only with necessity and ownership evidence; pair every created worktree with a cleanup path.

Announce at start: explain which concrete checkout conflict requires a worktree.

Step 0: Environment Detection

Before mutation, record the repository root, HEAD, branch/detached state, staged/unstaged/untracked paths, active Git operations, and:

git worktree list --porcelain

This is the opening of the README. Read the full README on GitHub.

Commands Using Git Worktrees provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/branch

Frequently asked about Using Git Worktrees

What else does GanyuanRan publish alongside Using Git Worktrees?
Using Git Worktrees is one of 22 skills that DirSkills catalogs from GanyuanRan/Aegis, the repository it ships in. Its siblings there include Aegis Goal Framing, Anti-Entropy Governance and Brainstorming. Each one is a separate skill with its own page in this directory, installs the same way Using Git Worktrees does, and is maintained by GanyuanRan in that same repository. The rest of the collection is listed on the GanyuanRan/Aegis page.
How does Using Git Worktrees compare to other DevOps skills?
Using Git Worktrees ranks #420 by stars among the 798 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Using Git Worktrees against them. Open each page to compare what they document and how they install.