worktree

Create git worktrees with gh wt add after plan approval.

1|1|Updated Nov 27, 2025

Search Tags:#automation #git #workflow #development #branching #worktree

Ready to run

npx skills add https://github.com/HikaruEgashira/agent-skills --skill worktree-hikaruegashira

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/HikaruEgashira/agent-skills/tree/main/wf/skills/worktree
Command: npx skills add https://github.com/HikaruEgashira/agent-skills --skill worktree-hikaruegashira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan approved or completed triggers autonomous creation of a dedicated git worktree to streamline parallel workstreams.

Core Features & Use Cases

Create a new git worktree for a given branch using gh wt add <branch>.
Enforce branch naming rules (no slash characters) to maintain repository hygiene.
Automatically trigger the next workflow step commit-push-pr-flow after worktree creation.

Quick Start

Create a git worktree for the specified branch after plan approval using gh wt add <branch> and then invoke commit-push-pr-flow.

Frequently Asked Questions about worktree

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

FAQPage Schema

How do I automate git worktree creation after a plan is approved?▼

The worktree Skill automates git worktree creation by triggering gh wt add for a specified branch after plan approval. It streamlines parallel development workflows by autonomously preparing isolated workspaces without manual intervention, then initiates the commit-push-pr-flow.

What are the branch naming rules when creating a git worktree with automation?▼

Branch naming rules for automated git worktree creation prohibit slash characters to maintain repository hygiene. The worktree Skill enforces this constraint during the gh wt add execution to ensure branches comply with the required naming format before proceeding.

Can I trigger a commit-push-pr workflow automatically after setting up a git worktree?▼

You can trigger a commit-push-pr workflow automatically after setting up a git worktree using the worktree Skill. Once the worktree is created via gh wt add, it invokes the commit-push-pr-flow to continue the software development automation sequence.

When do I need to create an isolated git worktree for parallel development tasks?▼

You need to create an isolated git worktree when working on parallel development tasks that require separate workspaces. The worktree Skill automates this process after plan completion, allowing teams to manage multiple branches simultaneously without switching directories.

Does the worktree automation require any specific dependencies or components to run?▼

The worktree automation requires no specific dependencies or components to run. It operates independently to execute gh wt add commands and enforce branch naming rules, relying only on the existing git environment within your software development workflow.