shipping-worktree

Automate shipping Git worktree changes to the main branch.

13|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/davidabeyer/formaltask --skill shipping-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-worktree
Source: https://github.com/davidabeyer/formaltask/tree/main/skills/shipping-worktree
Command: npx skills add https://github.com/davidabeyer/formaltask --skill shipping-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the entire process of taking changes from a git worktree, from initial review and committing to creating a pull request, merging it, and cleaning up the worktree and branch.

Core Features & Use Cases

  • Automated Git Workflow: Manages the end-to-end process of shipping code from a worktree.
  • Change Review & Committing: Facilitates review of changes and commits them in logical groups.
  • PR Creation & Merging: Creates pull requests, handles merging (defaulting to squash merge), and cleans up remote and local branches.
  • Worktree Cleanup: Ensures no orphaned worktrees are left behind.

Quick Start

Use the shipping-worktree skill to ship your current worktree.

Frequently Asked Questions about shipping-worktree

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

FAQPage Schema
How do I automate shipping code changes from a git worktree to the main branch?

To ship git worktree changes, the workflow reviews and commits changes, creates a pull request, merges it to the main branch, and cleans up the local and remote branches plus the worktree.

What is the best way to clean up orphaned git worktrees after merging a pull request?

The best way to clean up git worktrees is to automate the deletion of local and remote branches and remove the worktree directory after the pull request merge completes.

How do I commit changes in logical groups before creating a pull request from a worktree?

To commit changes in logical groups, you review the worktree changes, stage related modifications together, and commit them using conventional commit messages before pull request creation.

Does shipping a git worktree to production require user confirmation during the workflow?

Yes, the git worktree shipping workflow enforces user confirmation at critical stages like committing changes and merging the pull request to adhere to Git best practices.

Can I use squash merge when shipping changes from a git worktree to the main branch?

Yes, squash merge is supported and set as the default merge strategy when creating and merging the pull request from your git worktree changes to the main branch.