worktree-merge-manager

To safely merge a git worktree, the skill enforces a clean-state check, summarizes changes, and requires explicit human confirmation before merging into the main branch and performing deterministic cleanup.

You can discard an unwanted git worktree safely because the skill checks for a clean repository state and requires explicit confirmation, preventing accidental data loss during the discard action.

The best way to clean up finished feature work in a git worktree is to use a skill that validates the repository state, summarizes changes, and requires explicit confirmation before merging or discarding.

Yes, merging a worktree requires explicit human confirmation; the skill summarizes changes and checks for a clean state to ensure only explicitly approved actions are executed.

Validating repository state before discarding a git worktree prevents accidental data loss by ensuring uncommitted changes are addressed and requiring explicit confirmation before cleanup.