What problem does it solve? Git worktree workflows fail most often at lifecycle boundaries: creating worktrees for trivial changes, splitting commits across branches, losing work by removing worktrees before squash merges land, or polluting shared databases. This Skill identifies which lifecycle stage you are in and provides the exact inspection steps, decision trees, and checklists for that stage. ## Core Features & Use Cases - Stage Identification: Classifies the current state into setup, working, prep, or cleanup by inspecting git status, worktree list, and repo policy docs instead of asking the user. - Fast-Path Decision Tree: Determines whether a change qualifies for a single-commit fast-path on the integration branch or requires a full worktree, based on change type (schema, dependency, cross-package) rather than size intuition. - Safe Cleanup Ordering: Enforces squash-verification via commit-hash ancestor checks before worktree removal, logical DB drop, and branch deletion to prevent work loss. - Use Case: Before merging a feature, ask whether the worktree can be removed; the Skill verifies the squash commit landed on the integration branch, then walks through worktree removal, DB drop, and branch deletion in the correct order. ## Quick Start Ask the assistant to decide whether a new task needs a worktree or can be done as a fast-path commit, or to verify it is safe to clean up a finished worktree.
