worktrunk

Configure and troubleshoot Worktrunk CLI for managing Git worktrees.

2|Updated Aug 1, 2024
One-click install
npx skills add https://github.com/Kabilan108/dotfiles --skill worktrunk-kabilan108
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktrunk
Source: https://github.com/Kabilan108/dotfiles/tree/main/agents/skills/worktrunk
Command: npx skills add https://github.com/Kabilan108/dotfiles --skill worktrunk-kabilan108

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides expert guidance for configuring and troubleshooting Worktrunk, a CLI for managing Git worktrees, including setup, everyday usage, and debugging.

Core Features & Use Cases

  • Guidance on user config ( ~/.config/worktrunk/config.toml ) and project config ( .config/wt.toml ), plus common workflows like switch, merge, and remove
  • Troubleshooting strategies for shell integration, approvals, and status tracking across multiple worktrees
  • Use cases for automating setup, hooks, and cross-worktree automation

Quick Start

Install shell integration, create user and project configs, and start using core commands such as wt switch, wt merge, and wt list to manage multiple worktrees.

Frequently Asked Questions about worktrunk

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

FAQPage Schema
How do I configure git worktrees for multi-branch workflows?

You configure git worktrees by creating a user config at ~/.config/worktrunk/config.toml and a project config at .config/wt.toml. This setup manages multiple worktrees, automating switch, merge, and remove workflows across local repositories.

What is the best way to automate shell integration for git worktrees?

Automating shell integration involves installing the CLI's shell hooks to track status across multiple worktrees. This enables automated approvals and streamlines cross-worktree automation directly within your local shell environment.

How do I set up hooks for automated commit message generation in worktrees?

You set up hooks for commit message generation by configuring project-level settings in .config/wt.toml. This automates commit message workflows and applies hooks uniformly across all linked worktrees in your repository.

Why is my git worktree status not tracking correctly across branches?

Git worktree status tracking fails when shell integration is missing or user configurations are mismatched. Troubleshoot by verifying your ~/.config/worktrunk/config.toml and ensuring shell integration hooks are properly installed.

Can I manage multiple git worktrees without manual directory switching?

Yes, you can manage multiple git worktrees without manual switching by using the wt switch and wt list commands. These rely on your config.toml settings to automate directory navigation and status tracking.

Do I need TOML configuration files to use git worktree automation?

Yes, TOML configuration files are required for git worktree automation. The user config at ~/.config/worktrunk/config.toml and project config at .config/wt.toml define the hooks, shell integration, and workflows for your repositories.