git-cleanup

To clean up stale git branches and worktrees, the skill audits repositories using dev as the integration branch to find items merged via standard or squash strategies, then performs user-confirmed safe deletions. It checks for uncommitted changes to prevent data loss.

Yes, git branch cleanup works with squash merge strategies. The skill audits local and remote origin branches to detect those fully merged into dev, handling both standard and squash merge tracking for accurate stale branch identification.

Stale worktree detection prevents data loss by checking for uncommitted changes and dirty worktree states before any action. It presents a summary of merged items for user confirmation, executing deletions only on approved clean branches and worktrees.

The best way to remove obsolete remote origin branches is fetching remote state to verify merge status into dev. The skill audits origin branches, confirms safe deletion with the user, removes stale items, and appends results to a cleanup log file.

You can automate post-merge housekeeping by invoking the skill to audit local branches against the dev branch. It identifies fully merged local branches, checks for dirty worktrees, and executes safe deletions after user confirmation to maintain repo hygiene.

A limitation of automated git cleanup is its specific requirement for repositories using dev as the integration branch. It relies on git commands for fetching remote state and merge status checks, requiring user confirmation to safely delete only clean, merged items.