wt

Automate Git worktree creation, switching, listing, and cleanup via CLI.

5|7|Updated Jul 21, 2014
One-click install
npx skills add https://github.com/lucidash/dotfiles --skill wt-lucidash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wt
Source: https://github.com/lucidash/dotfiles/tree/main/claude/skills/wt
Command: npx skills add https://github.com/lucidash/dotfiles --skill wt-lucidash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the management of Git worktrees, enabling faster creation, switching, listing, and cleanup across multiple feature branches without manual context switching.

Core Features & Use Cases

  • Create/Switch Worktrees: Rapidly create and switch to a specific branch as a dedicated worktree.
  • List & Status: Inspect all worktrees, their branches, and pending changes in one view.
  • Handoff & Sessions: Prepare and share session context for collaboration across worktrees.
  • Pr-Integrated Workflow: Retrieve PR details for current worktrees when used with the GitHub CLI.

Quick Start

wt /wt list /wt feature/LK-1234 /wt LK-1234 /wt 2 /wt -q feature/LK-1234

Frequently Asked Questions about wt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Git worktree creation and switching for feature branches?

The Skill parses branch names or ticket IDs from the CLI to instantly create and switch to a dedicated Git worktree for that feature branch.

What is the best way to list all Git worktrees and check their pending status?

Listing Git worktrees involves a single CLI command that aggregates all active worktrees, their associated branches, and pending changes into one unified view for inspection.

Can I retrieve GitHub PR data for the current Git worktree?

Yes, you can retrieve GitHub PR data for the current worktree because the Skill integrates with the GitHub CLI (gh) to fetch PR details directly linked to the active worktree branch.

How do I prepare a session handoff across multiple Git worktrees?

Preparing a session handoff uses CLI commands that package and share the current worktree context, enabling seamless collaboration and context transfer across multiple worktrees.

Do I need the GitHub CLI to manage worktrees with this automation?

You do not need the GitHub CLI for core worktree management like creating, listing, and cleaning. The gh integration is only required when retrieving PR details for your current worktree.

How do I clean up unused Git worktrees from the command line?

You clean up unused Git worktrees by running a dedicated clean command via the CLI, which automates the removal of stale worktrees to keep your feature branching workflow organized.