post-merge-cleanup

You can automate git cleanup after a PR merge by running the post-merge-cleanup command with your task ID. It removes worktrees, local branches, and remote branches, and updates task statuses in STATUS.md or Linear with safety checks and dry-run previews.

To clean up git worktrees and local branches automatically, use a post-merge cleanup tool that detects merged PRs and removes associated worktrees and branches. This Skill also verifies the PR merge status before deletion and supports dry-run mode to preview changes safely.

Yes, post-merge cleanup works with Linear issue tracking alongside filesystem-based STATUS.md. It auto-detects the task source based on the task ID pattern and updates the issue status consistently after a PR merge, keeping both tracking systems in sync.

Yes, you can preview git branch deletion before running cleanup using the built-in dry-run mode. This allows you to verify which worktrees, local branches, and remote branches will be removed and what status updates will occur without making actual changes.

Yes, it is safe to run post-merge git cleanup multiple times because the operation is idempotent. Repeated executions will not cause errors or duplicate actions, and built-in PR verification and confirmation prompts ensure no unmerged work is accidentally deleted.

The best way to update task status in STATUS.md after merging a PR is to use an automated cleanup tool that commits and pushes status changes directly. This Skill detects the task ID, updates the STATUS.md file, and can commit and push the changes to keep your repository current.