worktrunk

Coordinate parallel git worktrees with a unified CLI and lifecycle hooks.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill worktrunk-tomzx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktrunk
Source: https://github.com/tomzx/agents/tree/main/skills/worktrunk
Command: npx skills add https://github.com/tomzx/agents --skill worktrunk-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handling multiple parallel git worktrees manually is error-prone and hard to scale.

Core Features & Use Cases

  • Unified worktree lifecycle: switch, create, merge, and remove across branches.
  • Hooks and config: per-repo project hooks, user hooks, and LLM-assisted prompts for commit messages.
  • Per-branch state and logs: collect CI status, logs, and summaries for dashboards.

Quick Start

Create a new worktree and start its lifecycle with wt switch --create <branch>.

Frequently Asked Questions about worktrunk

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

FAQPage Schema
How do I manage multiple git worktrees in parallel without errors?

You can manage parallel git worktrees using a unified CLI that coordinates switch, create, merge, and remove workflows with automated lifecycle hooks to prevent manual errors.

Can I use hooks to automate git worktree lifecycle workflows?

Git worktree lifecycle hooks automate workflows by applying per-repo project hooks and user hooks, enabling per-branch state, logs, and optional AI-generated commit prompts across operations.

How do I create a new git worktree and switch to it from the command line?

To create a git worktree and start its lifecycle, you run the switch command with the create flag for your target branch, which requires local config and shell integration to automate directory changes.

Do I need a local configuration file to manage git worktrees with hooks?

Yes, managing git worktrees with hooks requires a local configuration setup for both user and project levels, alongside shell integration to execute directory changes and hook automation correctly.

What is the best way to collect CI status and logs for different git worktrees?

The best way to collect per-branch state and logs for git worktrees is using a CLI that aggregates CI status, logs, and summaries for dashboards across parallel branches.

Why does handling multiple git worktrees manually not scale?

Handling multiple parallel git worktrees manually is error-prone and hard to scale because it lacks a unified CLI and automated hooks to coordinate per-branch state, logs, and lifecycle workflows.