Menu
Find and remove git worktrees whose PRs have been merged to main. Use when the user says "clean worktrees", "prune worktrees", or wants to tidy up stale worktree branches.
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
Take a set of local feature branches/worktrees all the way to merged PRs — discover unmerged work, fix commit-time hygiene, push, raise PRs, watch CI, auto-fix mechanical failures, merge on green, and cascade-rebase the rest. Use when the user says "shepherd PRs" or wants several branches driven to merge autonomously.
Read BEFORE invoking `playwright test` in any form, for any reason — running e2e, visual regression, room snapshots, or verifying a change 'via e2e'. Covers required project scoping (chromium-desktop, matching CI), the sandbox browser-build bridge, and the pnpm webServer failure. Also load on these failure signatures: every test failing at browserType.launch, 'Executable doesn't exist at /opt/pw-browsers/...', or 'Process from config.webServer was not able to start'.
Run the true-site-size GitHub Action locally via `act` inside the Claude Code web sandbox, to measure the game/editor cold-load journey byte cost without a CI round-trip. Use when asked to measure or verify build/wire size, or to check a byte-saving change, in the sandbox.
Fetch a campaign from the Supabase DB and save as local JSON. Use when the user asks to load, download, or fetch a campaign from the database.
Drive the Head over Heels remake's UI via the chrome-devtools MCP. Use this skill when the user asks for browser automation, capturing localStorage, dispatching game actions, or anything that involves driving the running game on localhost.
Run Docker — and tools that need it, like `act` (local GitHub Actions) — inside the Claude Code web sandbox, where image pulls and in-container networking collide with the egress proxy. Use when `docker pull` returns 403 on image layers, when a container can't reach the network, or when running `act`/CI-in-docker locally (e.g. the `act-true-site-size.sh` script).
| name | clean-worktrees |
| description | Find and remove git worktrees whose PRs have been merged to main. Use when the user says "clean worktrees", "prune worktrees", or wants to tidy up stale worktree branches. |
git worktree list
For each branch (excluding the main working directory and any non-worktree directories like hohjs-e2e-coverage), check whether its PR has been merged:
gh pr list --head "<branch>" --state merged --json number,title,mergedAt
Separate worktrees into two groups: merged and unmerged.
NEVER remove unmerged worktrees unless the user explicitly names them and asks for removal.
For each unmerged worktree, report:
git -C <path> log --oneline origin/main..<branch> to show what's been committedgit -C <path> status --short to show any dirty statePresent this as an informational summary so the user can decide what to do with them.
For each merged worktree, check git -C <path> status --short. Separate into:
git worktree remove <path>
Present each dirty worktree's uncommitted changes to the user. Only force-remove (git worktree remove --force <path>) after explicit approval for each one.
After removal, clean up any stale worktree metadata:
git worktree prune