wts-expert_skill

Overview

This skill is an expert assistant for @desplega.ai/wts, a CLI for managing Git worktrees with tmux and Claude Code integration. I guide users through creating, switching, cleaning, and using worktrees to run multiple branches concurrently. The goal is to make branch-based multitasking simple and reproducible across projects.

How this skill works

I inspect the current repository and wts installation status, validate project registration, and recommend the exact wts commands to run. I preview commands before execution and provide step-by-step workflows for creating worktrees, launching tmux/Claude, creating PRs, and cleaning merged worktrees. I also check configuration files (~/.wts.json and .wts-config.json) to suggest project-specific overrides.

When to use it

• Starting a new feature branch and you want an isolated working directory
• Switching between multiple active branches without stashing or switching HEAD
• Creating a GitHub PR directly from a worktree
• Cleaning up worktrees that have been merged or are stale
• Automating dev environment setup with tmux and Claude Code on worktree creation

Best practices

• Run which wts or npm list -g @desplega.ai/wts before issuing wts commands to confirm installation
• Initialize each repository with wts init so the project is tracked in ~/.wts.json
• Use descriptive aliases and date prefixes (wts creates .worktrees/<proj>/<date>-<alias>) for easy discovery
• Prefer wts create --new-branch when starting features and wts cleanup --dry-run before deleting
• Keep project overrides in .wts-config.json for repeatable post-create setup scripts

Example use cases

• Create a new feature worktree and open it in tmux with Claude Code: wts create my-feature --new-branch --tmux --claude
• Switch between active feature branches using an interactive fzf picker: wts switch
• Open a draft pull request from the current worktree and launch it in the browser: wts pr --draft --web
• List all tracked worktrees and remove those merged over 30 days ago: wts list && wts cleanup --older-than 30
• Recover from conflicts: list worktrees, switch to the problematic worktree, run fixes, then create a PR