pop-worktree-manager

Manage Git worktrees across projects with structured JSON output.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jrc1883/popkit-ai --skill pop-worktree-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pop-worktree-manager
Source: https://github.com/jrc1883/popkit-ai/tree/main/packages/popkit-dev/skills/pop-worktree-manager
Command: npx skills add https://github.com/jrc1883/popkit-ai --skill pop-worktree-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Git worktree management is complex when developing across multiple branches. This skill provides a project-wide solution for creating, listing, switching, updating, pruning, and analyzing worktrees with safety checks and STATUS.json integration.

Core Features & Use Cases

  • Multi-operation CLI: list, create, remove, switch, update-all, prune, init, analyze.
  • Cross-platform path handling via pathlib and Windows long-path support.
  • STATUS.json integration for morning routines and next actions.

Quick Start

Run python scripts/worktree_operations.py --operation list to view current worktrees.

Frequently Asked Questions about pop-worktree-manager

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

FAQPage Schema
How do I manage multiple Git worktrees for parallel development on feature branches?

You can manage Git worktrees across multiple branches by running a multi-operation CLI that lists, creates, switches, and prunes worktrees. This enables parallel feature development without continuous checkout churn, returning structured JSON results.

What is the safest way to remove or switch Git worktrees without losing critical branch data?

Safe Git worktree removal and switching is enforced through built-in protection on critical branches. The operations validate paths and branch states before execution, ensuring critical branch data is preserved during worktree transitions.

Does Git worktree management work on Windows with long path limitations?

Git worktree management supports cross-platform path handling using pathlib, including explicit Windows long-path support. This ensures consistent worktree creation, analysis, and pruning operations across different operating system environments.

How do I integrate Git worktree status into a morning routine or next actions workflow?

Git worktree status integrates directly into a morning routine by reading and writing to a STATUS.json file. The CLI updates this file during operations, providing a structured JSON snapshot of current worktrees and next actions.

Why does my Git worktree CLI return structured JSON instead of throwing exceptions?

Git worktree CLI operations return structured JSON instead of exceptions to provide predictable, machine-readable error handling. This design choice ensures automation scripts can reliably parse execution outcomes without catching runtime exceptions.

How do I prune and update all Git worktrees across a project at once?

You can prune and update all Git worktrees across a project by executing the update-all and prune CLI operations. These commands systematically clean stale worktree references and synchronize active worktrees across your branches.