worktrunk

Automate worktree lifecycle management and parallel-agent orchestration with Worktrunk.

1|1|Updated May 3, 2026
One-click install
npx skills add https://github.com/matt-riley/agent-skills --skill worktrunk-matt-riley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktrunk
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/worktrunk
Command: npx skills add https://github.com/matt-riley/agent-skills --skill worktrunk-matt-riley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Worktrunk provides structured guidance to configure and operate worktrees, hooks, and parallel agent workflows, reducing manual setup and the risk of misconfiguration.

Core Features & Use Cases

  • Centralized configuration for worktree management and per-repo setups, enabling isolated worktrees for concurrent tasks.
  • Setup of LLM-generated commit messages and project hooks (post-start, pre-merge, etc.) across multiple worktrees.
  • Coordination of parallel agent lanes with consistent naming, port allocation, and lifecycle management for multi-branch scenarios.

Quick Start

Configure Worktrunk for this repository and initialize a parallel worktree workflow across multiple agent lanes.

Frequently Asked Questions about worktrunk

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

FAQPage Schema
How do I manage git worktrees for parallel agent workflows?

To manage git worktrees for parallel agent workflows, you can use an orchestration tool that automates worktree lifecycle management, enabling isolated branches for concurrent tasks across multiple agent lanes.

What is the best way to automate worktree lifecycle management across local repos?

Automating worktree lifecycle management across local repos is best handled by applying centralized configuration with per-repo setups, which reduces manual setup and prevents misconfiguration.

Can I configure per-worktree hooks and LLM-generated commit messages?

Yes, you can configure per-worktree hooks and LLM-generated commit messages, applying project hooks like post-start and pre-merge consistently across multiple worktrees.

How do I coordinate port allocation and naming for multi-branch worktree scenarios?

You coordinate port allocation and naming for multi-branch scenarios by using parallel-agent orchestration that applies consistent naming conventions and lifecycle management across worktrees.

Does this worktree orchestration approach require specific dependencies?

This worktree orchestration approach operates without specific dependencies, providing workflow guidance and validation points directly for wt config, per-worktree commands, and hook definitions.