release-worktree

Release git worktrees after PR creation and log in centralized tracking files.

1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/martiendejong/autonomous-dev-system --skill release-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-worktree
Source: https://github.com/martiendejong/autonomous-dev-system/tree/main/.claude/skills/release-worktree
Command: npx skills add https://github.com/martiendejong/autonomous-dev-system --skill release-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release worktrees after PR creation and before presenting results to the user. It coordinates cleanup, seat management, state transitions, and ensures all tracking files are updated in a zero-tolerance workflow across multiple repositories. It enforces strict post-PR release steps, prunes git worktrees, and logs the release in centralized tracking files.

Core Features & Use Cases

  • Zero-tolerance protocol enforcement for post-PR release
  • Automated worktree cleanup and resource release
  • Centralized logging and state management across repos
  • Use Case: After a feature branch PR is opened and merged, this skill cleans the worktree and returns the base repos to develop.

Quick Start

Run this skill immediately after a PR is created to safely clean up the worktree and free the associated resources.

Frequently Asked Questions about release-worktree

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

FAQPage Schema
How do I automate git worktree cleanup after a pull request?

Automate git worktree cleanup after a pull request by running a zero-tolerance protocol that prunes worktrees, manages seat states, and logs releases. It ensures safe resource release before presenting PR results to the user.

What is the best way to manage worktree state transitions across multiple repositories?

Managing worktree state transitions across multiple repositories requires centralized tracking files to coordinate cleanup and seat management. It enforces strict post-PR release steps to ensure all repos return to develop.

How do I prune git worktrees safely before showing PR results?

Prune git worktrees safely before showing PR results by enforcing strict post-PR release steps. The workflow coordinates cleanup, prunes git worktrees, and logs the release in centralized tracking files across multiple repos.

Does automated worktree release work with multi-repo workflows?

Automated worktree release works with multi-repo workflows by coordinating cleanup and state transitions across all repositories. It updates centralized tracking files and returns the base repos to develop after PR creation.

When should I run automated worktree release in my git workflow?

Run automated worktree release immediately after a feature branch PR is created. Running it at this point safely cleans the worktree, frees associated resources, and returns base repos to develop before presenting results.

Why do I need centralized tracking files for worktree cleanup?

Centralized tracking files are needed for worktree cleanup to log releases and manage seat states across multiple repositories. They enforce a zero-tolerance workflow by ensuring all state transitions are recorded accurately.