feature-teardown

To safely delete a git worktree and local feature branch, you need a teardown process that verifies worktree existence, checks for uncommitted changes, removes the worktree, deletes the branch, and prunes stale references.

When removing a git worktree, uncommitted changes are detected during the process and appropriate prompts are triggered to ensure no local modifications are lost before the feature branch and worktree are deleted.

Yes, you can clean up feature branches and worktrees across multiple local development repositories by running a teardown operation that prunes stale references and removes local infrastructure for each finished feature.

The best way to clean up stale git worktree references is to use an automated teardown workflow that removes the feature-specific worktree, deletes the local branch if safe, and prunes lingering references for a clean local repo state.

You should not use an automated git worktree removal process if your feature is not yet finished, as this teardown operation is infrastructure-only and deletes local feature branches without checking the feature's completion status.