메뉴
Plan and (only after user confirmation) delete remote and matching local git branches whose PR is already merged or closed (not merged) and that have no remaining commits or file changes. Use when the user asks to clean up, prune, or delete merged/closed branches (브랜치 정리, cleanup branches, delete merged branches).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Applies project TypeScript conventions and library-grade module boundaries. Use when writing or editing .ts/.tsx files, designing exported APIs or cross-layer contracts, creating reusable modules, or refactoring dependencies between features, packages, services, and adapters.
Analyze project vulnerabilities with pnpm audit and resolve them automatically when a fix version is available; report unfixable deep dependency issues.
Remove safe git worktrees that have no uncommitted changes and no commits missing from a pull request. Use when the user asks to clean up, prune, or remove worktrees (워크트리 정리, worktree cleanup).
Applies project conventions for Solid.js components, custom hooks, reactivity, and styling. Use when writing or editing Solid.js .tsx/.ts files.
Write and refine Korean text in developer contexts — code comments, AIDEV-NOTE anchors, commit messages, PR descriptions, review replies, design docs, memory notes — so it reads as natural, grammatical Korean a native engineer would write, not as awkward literal translation, broken word order, or forced metaphor. Use whenever producing Korean prose for engineering work, and especially self-review Korean output before finalizing.
Reduce an existing Codex skill to its minimum useful form, extract on-demand context into linked sibling files, or decide that the skill should be deleted. Use when the user asks to diet, slim, trim, simplify, minimize, reevaluate, or remove bloat from a skill while preserving its trigger behavior, tone, safety constraints, and practical usefulness.
| name | cleanup-branches |
| description | Plan and (only after user confirmation) delete remote and matching local git branches whose PR is already merged or closed (not merged) and that have no remaining commits or file changes. Use when the user asks to clean up, prune, or delete merged/closed branches (브랜치 정리, cleanup branches, delete merged branches). |
Delete remote branches whose PR is already merged or closed (not merged)
and that have no leftover commits or file changes. Delete matching local
branches too. Never delete main or dev.
Plan first. Show what would be deleted; delete only after the user explicitly asks to delete.
Delete only when all are true; otherwise skip and say why:
main or dev (local or origin/*)gh pr list --head <branch> --state open)gh pr list --head <branch> --state mergedgh pr list --head <branch> --state closedgit merge-base --is-ancestor <tip> <prHeadRefOid>
(prefer origin/<branch> tip; squash/rebase → do not require ancestry on
dev/main)status --porcelain empty); dirty → skip local onlyNever force-push or rewrite history. Use git branch -D only after the PR
checks (plain -d often fails after squash).
git fetch --prune originorigin (exclude main/dev/HEAD), plus
local-only branches with the same checksgit push --delete or git branch -D.git push origin --delete <branch>; matching safe local →
git branch -D <branch>; report removed vs skipped.Would delete:
- origin/<branch> — merged PR #<n>
- origin/<branch> — closed PR #<n> (not merged)
- <branch> (local) — matched origin / merged PR #<n>
Skipped:
- <branch> — <reason>
After confirmation, use the same shape with Removed: instead of Would delete:.