메뉴
Inspect and clean stale branches across multiple repositories using the dotfiles git-hygiene + gh-bootstrap toolchain. Use when the user asks about branch state, stale local branches, or "no ref was fetched" errors.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Full-lifecycle orchestration for comprehensive, no-compromise execution — roll-calls the right skills, fans out parallel/worktree agents, then closes the loop (verify, review, simplify, changelog, handoff, retro). Use when you want maximum effort, to go all-in, or to orchestrate a big task end-to-end.
Runs a short retrospective that PROPOSES edits to the user's Claude Code skills — capturing a newly-found gotcha, fixing a description that didn't auto-trigger, retiring a dead skill, or extracting a reusable pattern into a new skill. Improves the TOOLSET, not the session log. Use when the user signals satisfaction at the end of real work ("thanks", "thanks that worked", "that worked great", "nice", "perfect", "exactly what I needed"), or when they explicitly run /session-retro. Always proposes and waits for confirmation — never edits skills silently. In unattended runs (/orchestrate, overnight, or /session-retro --auto), writes proposals to ~/.claude/retro-proposals/ instead of blocking.
Generate a concise session handoff for resuming work later, including current state, decisions, open issues, and next steps.
Deep task decomposition into parallel workstreams with self-contained agent prompts. Use when you want to review the execution plan before committing to it.
Generate a handoff note for clean session transitions — preserves context across /clear or new sessions. Use when ending a session, when context is getting high, or when the user says "hand off", "wrap up the session", or "save state for next time".
Update a project CHANGELOG.md or equivalent session log with concise notes about completed changes, decisions, and known issues.
| name | branch-hygiene |
| description | Inspect and clean stale branches across multiple repositories using the dotfiles git-hygiene + gh-bootstrap toolchain. Use when the user asks about branch state, stale local branches, or "no ref was fetched" errors. |
The user has a three-layer auto-hygiene system in ~/dev/dotfiles/:
gh-bootstrap.sh): every repo has
delete_branch_on_merge=true, allow_auto_merge=true (Git Pro),
allow_update_branch=true, and a squash-only merge policy with
squash_merge_commit_title=PR_TITLE / squash_merge_commit_message=PR_BODY.git-hygiene.timer, fires 09:30 local) — runs
gh-bootstrap.sh --check --all ~/dev and writes drift state to
~/.local/state/hygiene/status.json. On Sundays it also runs
git-hygiene.sh clean ~/dev --yes to delete locally-merged branches.gh wrapper in .bash_aliases — when the user runs
gh repo create or gh repo clone from their shell, the wrapper auto-runs
gh-bootstrap.sh on the new repo. Note: this only fires from the user's
interactive shell, not from agent-spawned shells.When the user asks about hygiene state:
~/.local/state/hygiene/status.json first — it's the cached daily
check. Use ~/dev/dotfiles/hygiene-status.sh --status for a one-liner or
--text for a full readout. This is read-only and instant.~/dev/dotfiles/gh-bootstrap.sh --check --all ~/dev.~/dev/dotfiles/git-hygiene.sh clean ~/dev --yes.~/dev/dotfiles/gh-bootstrap.sh <owner/repo> or --all <dir>.If you (the Codex agent) run gh repo create or gh repo clone yourself,
the shell wrapper does not fire — your gh invocation goes directly to the
binary. Run ~/dev/dotfiles/gh-bootstrap.sh <owner/repo> immediately
after any successful create/clone you do, so the new repo doesn't drift.
git-hygiene.sh confirms a local branch is merged via three independent
signals before deleting:
git cherry origin/<default> <branch> — patch-equivalent commitsorigin/<default> history
(catches squash collapses that cherry misses)gh pr list --state all --head <branch> returns MERGEDA branch is deleted only when at least one signal confirms merge. Dirty working trees, current branch, and worktree-checked-out branches are always skipped.
If the user just asks "is everything clean?":
$ ~/dev/dotfiles/hygiene-status.sh --status
clean (checked 4h ago)
If drift exists, the same command emits a summary and the user can run
gh-bootstrap.sh --all ~/dev to fix it. Be specific about which repos
drifted — they're listed in drifted_repos of the JSON.
After archiving or deleting a repo locally, also purge its Claude Code state (transcripts, file history, config entries, tasks) — this works from any shell, not just Claude sessions:
# Always dry-run first
claude project purge "$REPO_PATH" --dry-run
# When the dry-run looks right
claude project purge "$REPO_PATH" --yes
The --all flag purges every project not currently on disk in one pass —
useful after a quarterly cleanup. Without it, ~/.claude/projects/ and
~/.claude/file-history/ accumulate state for dead projects forever.