git-detect-merged

To identify merged branches, the Skill checks local branches against a target branch using standard merge-base and --merged checks. It applies a pre-filter to avoid deleting unrelated history before flagging branches for safe cleanup.

Detecting squash-merged branches involves combining single-commit cherry checks with patch-id comparisons. This confirms whether the changes are fully integrated into the target branch, enabling safe deletion of squash-merged work.

You should not automatically delete dirty worktrees. The Skill actively flags worktrees with untracked changes, dirty states, or active checkouts to prevent accidental deletion and preserve uncommitted work during cleanup.

Checking branch merge status requires a local Git environment and uses standard commands such as git branch, git merge-base, git cherry, and git patch-id to accurately classify both regular and squash merge statuses.

The best way to clean up stale branches and worktrees is to run the Skill against a target branch like main. It identifies both regular and squash-merged entries while protecting active work, guiding safe history preservation and pruning.