post-merged

What problem does it solve?

After merging a pull request, developers often leave behind messy local git state: unswitched branches, unpruned local feature branches, and unverified merge status, which can lead to accidental data loss or confusion in future work.

Core Features & Use Cases

• Remote Merge Verification: Uses GitHub CLI to confirm PR merge status, correctly handling squash and rebase merges that break local ancestry checks.
• Safe Default Branch Switching: Automatically detects the repository's default branch (no hardcoded main/master) and switches to it after pulling the latest changes with fast-forward only.
• Guarded Local Branch Deletion: Prompts for explicit user consent before deleting the local feature branch, using safe delete flags that refuse to remove branches with unmerged work, and surfaces orphaned [gone] branches for manual cleanup.
• Use Case: Immediately after shipping a feature branch PR, run this skill to automatically confirm the merge, update your local default branch, and clean up the old feature branch without risking lost work.

Quick Start

Use the post-merged skill right after you finish shipping a PR to handle all post-merge cleanup steps safely.