cleanup-stashes

To safely clean up git stashes, generate an approval script that categorizes them by branch existence, merge status, and age, excluding recent entries and targeting only orphaned, superseded, or stale ones for user-approved dropping.

You can identify and drop merged git stashes by analyzing stash metadata to flag entries whose target branch has been merged to main, then generating a ready-to-run drop script that targets these likely superseded stashes for your review.

The best way to remove orphaned git stashes is to classify them by branch existence, identifying stashes tied to deleted branches, and producing a safety-first drop script that requires your explicit approval before execution.

Yes, you can review git stashes before dropping them by generating a concise summary that lists all stashes with branch, age, and file details, returning a ready-to-run script for approval without executing any drop commands directly.

No, the stash cleanup script does not automatically delete old stashes; it flags stashes older than 14 days as likely forgotten and includes them in a generated drop script, requiring user approval to execute the removal.

You should use a generated script for stash management because it provides a safety-first approach by analyzing branch existence and merge status, returning a script for explicit user approval rather than permanently dropping stashes directly.