update-component-refer…
This skill should be used when the user wants to add components (commands, agents, skills, hooks, or MCP servers) to the Component Reference section of the…
This skill should be used when the user wants to manage Git worktrees - creating worktrees from local or remote branches, listing active worktrees with details, deleting worktrees, or switching between worktrees. Ideal for working on multiple branches simultaneously without
$ npx -y skills add NikiforovAll/claude-code-rules --skill git-worktree --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/git-worktreeContext preview
The summary Claude sees to decide when to auto-load this skill.
This skill should be used when the user wants to manage Git worktrees - creating worktrees from local or remote branches, listing active worktrees with details, deleting worktrees, or switching between worktrees. Ideal for working on multiple branches simultaneously without
name: git-worktree description: This skill should be used when the user wants to manage Git worktrees - creating worktrees from local or remote branches, listing active worktrees with details, deleting worktrees, or switching between worktrees. Ideal for working on multiple branches simultaneously without stashing changes.
This skill provides comprehensive Git worktree management capabilities, enabling work on multiple branches simultaneously in isolated directories. Worktrees eliminate the need for stashing when switching contexts and are ideal for parallel development, quick bug fixes, and code reviews.
Use this skill when the user wants to:
**Location Strategy**: Sibling directory pattern
**Naming Convention**: `<project>-<branch>`
**Hybrid Mode**: Accepts arguments when provided, prompts when missing
**Usage patterns**:
# Interactive menu User: "Manage my worktrees" User: "Create a worktree" # Direct with arguments User: "Create worktree from remote branch feature-x" User: "List all worktrees" User: "Delete worktree for branch hotfix-123"
**Purpose**: Show all active worktrees with detailed information
**What to display**:
**Implementation**:
# Get project name project=$(basename "$(git rev-parse --show-toplevel)") # List worktrees with details git worktree list -v
**Output format**:
Git Worktrees for myproject: 1. /Users/dev/myproject (main) abc1234 Initial commit [CURRENT] 2. /Users/dev/myproject-feature-x (feature-x) def5678 Add authentication logic 3. /Users/dev/myproject-hotfix (hotfix-123) 789abcd Fix login bug
**Purpose**: Fetch and create a worktree from a remote branch
**Steps**: 1. Validate we're in a git repository 2. Get project name: `project=$(basename "$(git rev-parse --show-toplevel)")` 3. Extract branch name from remote reference (e.g., `origin/feature-x` → `feature-x`) 4. Check if worktree already exists (warn and skip if it does) 5. Fetch remote branch: `git fetch origin <branch-name>` 6. Verify remote branch exists (check exit code) 7. Determine worktree path: `../<project>-<branch-name>` 8. Create worktree: `git worktree add ../<project>-<branch-name> origin/<branch-name>` 9. Show success message with path and navigation command
**Error handling**:
**Success output**:
✓ Created worktree for remote branch 'feature-x' Location: /Users/dev/myproject-feature-x Branch: feature-x (tracking origin/feature-x) To switch to this worktree: cd ../myproject-feature-x To start working: cd ../myproject-feature-x && code .
**Purpose**: Create a worktree from an existing local branch
**Steps**: 1. Validate we're in a git repository 2. Get project name 3. Verify local branch exists: `git rev-parse --verify <branch-name>` 4. Check if worktree already exists 5. Create worktree: `git worktree add ../<project>-<branch-name> <branch-name>` 6. Show success message with navigation
**Error handling**:
**Purpose**: Create a worktree with a brand new branch
**Parameters needed**:
**Steps**: 1. Validate we're in a git repository 2. Get project name 3. Get base branch (use current if not specified) 4. Check if worktree directory already exists 5. Create worktree with new branch: `git worktree add -b <new-branch> ../<project>-<new-branch> <base-branch>` 6. Show success message
**Success output**:
✓ Created new worktree with branch 'experiment-auth' Location: /Users/dev/myproject-experiment-auth Branch: experiment-auth (based on main) To switch to this worktree: cd ../myproject-experiment-auth
**Purpose**: Remove a worktree and show prune command
**Steps**: 1. If no branch specified, list all worktrees for selection 2. Verify worktree exists for specified branch 3. Remove worktree: `git worktree remove <path>` or manually `rm -rf <path>` 4. Show manual prune command (don't auto-execute per user preference)
**Output**:
✓ Removed worktree at /Users/dev/myproject-feature-x To clean up metadata, run: git worktree prune
**Purpose**: Clean up worktree metadata
**Steps**: 1. Run: `git worktree prune` 2. Show what was cleaned
**Output**:
✓ Pruned stale worktree metadata Run 'git worktree list' to see remaining worktrees.
**Purpose**: Show easy navigation to worktrees
**Implementation**: 1. List all worktrees (numbered) 2. Provide copy-ready cd commands
**Output**:
Available worktrees: 1. main (current) cd /User
A collection of Claude Code recommendations and practices. Learn practical techniques to enhance your AI-assisted development workflow with Claude Code.
This skill should be used when the user wants to add components (commands, agents, skills, hooks, or MCP servers) to the Component Reference section of the…
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump…
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured…
Review changed code for reuse, quality, and efficiency using three parallel disposable subagents. This skill should be used when the user says "review",…
Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. This skill should be used when the user says "team review",…
This skill should be used when users want to discover, browse, or audit cc-handbook marketplace plugins. Shows all available plugins with installation status,…