Menu
Use when the user wants to clean up stale or merged git worktrees under ~/.workspace (e.g. after PRs are merged and their remote branches deleted). Prunes workspaces whose remote branch is gone. Companion to pick-issue-to-pr.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | cleanup-workspaces |
| description | Use when the user wants to clean up stale or merged git worktrees under ~/.workspace (e.g. after PRs are merged and their remote branches deleted). Prunes workspaces whose remote branch is gone. Companion to pick-issue-to-pr. |
Remove git worktrees under ~/.workspace/<group>/<project>/<branch> whose upstream branch has been deleted on the remote (typically because the PR was merged). Companion to the pick-issue-to-pr skill, which creates those workspaces.
Scan ~/.workspace/ for <group>/<project>/<branch> directories. Group them by their main repository (the worktree's common git dir). For each distinct repository, run the steps below once.
git worktree list from any checkout of a repo lists all its worktrees with paths and branches — use it to get the authoritative list rather than relying on directory names alone.
For each repository:
git fetch --prune origin
This deletes remote-tracking refs for branches that no longer exist on the remote.
A workspace branch is a cleanup candidate when its upstream is gone:
git branch -vv
Branches whose upstream was pruned show : gone] in the output. Cross-check that the branch is actually merged or its PR is closed before removing — prefer : gone] (branch deleted on remote) as the signal, since that means the PR was merged or the branch was deleted intentionally.
Optionally confirm via the GitHub MCP / gh that the associated PR is merged/closed when in doubt.
For each confirmed candidate:
git worktree remove "<path>" # add --force only if it refuses due to untracked/modified files
git branch -D "<branch>" # the now-dangling local branch
Then tidy administrative files:
git worktree prune
Also remove now-empty <group>/<project> parent directories under ~/.workspace/.
List what was removed and what was kept (and why, e.g. uncommitted changes blocking removal). Never force-remove a workspace that has uncommitted or unpushed work without explicitly flagging it to the user and getting confirmation.
~/.workspace/.Bump package versions and update CHANGELOG.md so consumers can see what happens between releases. Use when a feature or fix branch is ready.
Pattern Libreary which allows representing graphical components. Provides CSS and uses HTML as a template language. This is where tokens, quarks, atoms, molecules, organisms, templates are defined.
Use when the user wants to pick a GitHub issue to work on from a list. Lists open issues (the ones already assigned to the current user first), lets the user choose one, self-assigns it, creates an isolated workspace, runs setup, clarifies the issue one question at a time, plans (one approval checkpoint), implements, opens a draft PR, and folds every later change — including review feedback — into a single amended commit.
Component Library with React components used by the application.