worktree-land

Merge worktree PRs into main and clean up associated worktrees.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/duanegoodner/agentrelay --skill worktree-land
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-land
Source: https://github.com/duanegoodner/agentrelay/tree/main/.claude/skills/worktree_land
Command: npx skills add https://github.com/duanegoodner/agentrelay --skill worktree-land

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge a worktree PR into main and clean up associated worktrees.

Core Features & Use Cases

  • Automates merging of PRs across worktrees with conflict handling via rebase when needed.
  • Cleans up worktrees and branches after PRs are merged.
  • Detects when the last PR in the batch is merged and triggers diagram re-rendering.

Quick Start

Merge a worktree PR into main and clean up associated worktrees after the batch completes.

Frequently Asked Questions about worktree-land

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

FAQPage Schema
How do I automate merging a git worktree pull request into main?

Automating a git worktree merge integrates PRs into main and cleans up associated worktrees. It handles merge conflicts by rebasing onto main and retrying until all batched PRs are successfully merged.

What happens when merge conflicts arise during a worktree PR batch integration?

When merge conflicts arise during worktree integration, the process automatically rebases the PR onto main and retries the merge. This loop continues until all PRs in the batch are successfully integrated.

How do I clean up git worktrees and branches after merging a pull request?

Cleaning up git worktrees after merging a pull request removes the associated worktree directories and branches automatically. This happens once the PR is successfully merged into the main branch.

Can I trigger diagram re-rendering automatically after the final PR in a batch is merged?

Yes, diagram re-rendering triggers automatically after the final PR in a batch is merged. The system detects the last merge, re-renders your diagrams, and commits any resulting updates to the repository.

What is the best way to manage multiple worktree PRs and ensure they integrate cleanly into main?

The best way to manage multiple worktree PRs is using an automated batch integration process. It merges each PR sequentially, resolves conflicts via rebase, cleans up worktrees, and commits diagram updates upon completion.