/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 -y skills add breaking-brake/cc-wf-studio --skill pr-to-main-cleanup --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/pr-to-main-cleanup
Context preview
The summary Claude sees to decide when to auto-load this skill.
Clean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.
SKILL.md
pr-to-main-cleanup.SKILL.mdname: pr-to-main-cleanup description: Clean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.
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
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
You think visually. AI thinks in .md. CC Workflow Studio speaks both. Design workflows on a canvas. Export as Markdown your AI agent already understands. No more prompt-guessing. Why CC Workflow Studio? - Speaker Deck Link
Repo: breaking-brake/cc-wf-studio
Other skills on cc-wf-studio.
- /jira-driven-planning
Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。
Open skill - /next-idea
Run one unattended IDEATION iteration of the autonomous value-creation loop — invent improvements a user of cc-wf-studio would notice, judge them against the value bar, and file the winners as locked `idea` issues. Never implements anything; the next-task skill builds from the
Open skill - /next-qa-idea
Run one unattended IDEATION iteration of the quality-assurance loop — find the highest-value untested behavior in the codebase, judge it against the QA value bar, and file ONE locked `qa` issue specifying the test to write. Never writes code or tests; the next-qa skill builds
Open skill - /next-qa
Run one unattended iteration of the QUALITY-ASSURANCE loop — steward any in-flight QA PR, then build ONE queued `qa` issue (test infrastructure, unit tests, regression tests for known bugs) on a branch off auto-qa and open a PR that squash-merges on green CI. Adds tests and
Open skill - /next-task
Run one unattended IMPLEMENTATION iteration of the autonomous value-creation loop — steward any in-flight PR, fix interrupts (red CI / security / human bugs), or else build ONE queued `idea` issue on a branch off auto-dev and open a PR that squash-merges on green CI. Ideation
Open skill - /pr-review-analysis
Analyze PR review comments from a GitHub PR URL. Fetch review comments, verify each finding against the actual codebase, assess validity (correct/incorrect/partial), present a structured summary with recommended actions, and optionally reply to each comment on GitHub. Use when
Open skill