Delete the `-bak` backup branches that `/prepare-merge` leaves behind, local and on origin, once the work they back up has merged. Use when the user says "remove my bak branches", "clean up bak branches", "delete the backups", or "/clean-bak-branches".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
-bak backup branches/prepare-merge saves the pre-squash history as <branch>-bak (-bak2,
-bak-20260917, … on reruns) and pushes it. Nothing removes those refs after
the PR merges, so they pile up. This skill removes the current user's ones.
-bak branch of the current user whose source PR is merged.--dry-run — list what would be deleted and stop.<pattern> — only branches whose name contains it (e.g. an issue number).git fetch --prune origin
me=$(git config user.email)
git for-each-ref --format='%(refname)|%(objectname:short)|%(authoremail)' \
refs/heads refs/remotes/origin \
| grep -E -- '-bak[0-9a-z-]*\|' | grep -F "<$me>"
Ownership is the author of the branch tip. The -bak refs of other people
are theirs to delete — never touch them, even when asked for "all".
A branch checked out in a worktree (git worktree list) is skipped and
reported.
Strip the -bak… suffix to get the source branch, then:
gh pr list --head <source-branch> --state all --json number,state
| Source PR | Action |
|---|---|
MERGED | delete |
OPEN, CLOSED unmerged, or no PR | keep, unless the user confirms via AskUserQuestion — the backup may be the only copy of the unsquashed history |
Print the name sha list first: it is the only way back
(git branch <name> <sha> works while the commits are still unreachable but
not yet collected).
git branch -D <local names…>
git push origin --delete <remote names…>
One git push --delete for all remote names, not one per branch.
Counts of local and remote refs deleted, what was kept and why, and a rerun of step 1 showing nothing of the user's is left.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when work on a branch is finished and the next step is a pull request — "create a PR", "open a PR", "push and PR this", "/create-pr" — when a draft PR should be marked ready for review — "mark the PR ready", "undraft it", "it's ready for review" — or right after either has happened and the team has not been told about it yet.
日本語の概要は準備中です。原文の説明を表示しています。
Search Google Cloud (GKE) server logs of the DEV environment (dev.voxt.ai). Use when troubleshooting anything that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check GCP logs", "check server logs on dev", or gives a dev.voxt.ai timeline from a client console log.
日本語の概要は準備中です。原文の説明を表示しています。
Search Google Cloud (GKE) server logs of the PROD environment. Use when troubleshooting a production incident that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check PROD logs", "check production server logs", or gives a production timeline from a client console log.
日本語の概要は準備中です。原文の説明を表示しています。
What this project has already learned the hard way, and where any new such fact belongs. Two jobs. (1) Routing: this project keeps NO per-project Claude memories — read this before writing anything down, and pick a durable home from the list here. (2) An index, by area, of non-obvious facts worth knowing before you guess: debugging rigs and measurements that lie, iOS/WebKit and the tethered iPhone, the Windows app, production and deployment, and general codebase traps. Use before setting up a browser- or server-driven debugging session, when a bug reproduces only on iPhone, in Safari or in the Windows app, before changing deployment configuration or reading store/crash data, when something behaves unexpectedly and you are about to guess why, and whenever you are tempted to record a fact for later.
日本語の概要は準備中です。原文の説明を表示しています。
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
日本語の概要は準備中です。原文の説明を表示しています。
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations.
日本語の概要は準備中です。原文の説明を表示しています。