pr-to-main-cleanup
Clean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.
npx skills add breaking-brake/cc-wf-studio --skill pr-to-main-cleanup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PR to Main Cleanup Delete merged feature branches after PR is merged to main. ## Workflow 1. **Gather context** (parallel): - `git branch` to identify current branch - `git log --oneline -1` to confirm current state 2. **Execute cleanup**: - Switch to main branch - Pull latest changes from origin - Delete local feature branch - Delete remote feature branch ## Commands ```bash git checkout main && git pull origin main && git branch -D <branch-name> && git push origin --delete <branch-name> ``` ## Important Notes - PRs to main are always squash-merged, so use `-D` (force delete) since git cannot detect squash merges as "merged" - Always pull latest main before deleting to sync merge status
- Workflow
- Commands
- Important Notes
git checkout main && git pull origin main && git branch -D <branch-name> && git push origin --delete <branch-name>
What does the pr-to-main-cleanup skill do?
Clean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.
How do I install it?
Run `npx skills add breaking-brake/cc-wf-studio --skill pr-to-main-cleanup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From breaking-brake/cc-wf-studio, a repository with 5,342 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.