architect
Use for design-level judgement: requirements, quality attributes, trade-offs, ADR, contracts, resilience, security,…
Use when a git worktree is dirty or another local branch or worktree exists. Ask before cleanup unless the session is unattended.
$ npx -y skills add ShaftHQ/SHAFT_ENGINE --skill git-cleanup --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/git-cleanupContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when a git worktree is dirty or another local branch or worktree exists. Ask before cleanup unless the session is unattended.
name: git-cleanup description: Use when a git worktree is dirty or another local branch or worktree exists. Ask before cleanup unless the session is unattended.
One checkout on the configured default branch. `HEAD` equals that remote tip. `git status` is clean.
The worktree is dirty, or another local branch or linked worktree exists.
Attended: ask first, and explain this procedure before changing anything. Unattended: decide and run it.
Name the configured default branch from the remote HEAD or the selected profile. Do not hardcode a repository branch name. This is the repository-scope recipe in cleanup-scopes. Do not fork a second policy.
1. Fetch and prune the configured upstream. Inventory dirty and untracked paths, extra local branches, linked worktrees, locks, and unique commits before mutation. 2. Classify each dirty or untracked path as land (commit, push, pull request, merge), delete, or gitignore. Halt on a locked or concurrently owned worktree. 3. Check out the configured default branch in the primary checkout and fast-forward it so `HEAD` equals the remote tip and `git status` is clean. 4. Remove extra linked worktrees only after that classification, and only when they are clean, unlocked, and not concurrently owned. Then remove a recreated local branch only when `git branch -r --contains` shows that exact tip on an origin ref. Also remove extra local branches that are fully merged into the remote tip, or whose unique commits were explicitly authorized for discard. 5. Check out the configured default branch and fast-forward it. Write the verification transcript in the same process, after that fast-forward. Do not check out another branch afterward.
One checkout, only the configured default branch, `HEAD` equals that remote tip, and `git status` is clean.
Do not stash. Do not `reset --hard`. Do not force-push. Do not use `--force-with-lease`. Do not delete remote branches. Do not rewrite remote history. Do not discard unique commits without explicit authorization. Do not commit generated plugin directories.
One Java engine for web, mobile, API, CLI, database, and desktop. Drivers, waits, and evidence are handled. Every run ends in an Allure report. Upgrade to SHAFT_ENGINE · ▶ Watch the 26-second clip with sound and captions · 100-second overview
Use for design-level judgement: requirements, quality attributes, trade-offs, ADR, contracts, resilience, security,…
Canonical provider-neutral skill router and working contract. Use at the start of every task, on every host, in every main thread…
Use when PR merge waits are long or CI/CD is being designed, audited, or sped up: targets, PR/main/nightly tiers, opt-in labels,…
Frontier MoE through a disk/RAM/VRAM hierarchy via the optional Colibri process. Use when a large-model offline job needs…
Standalone FreeToken process: install, READY probe and bounded dispatch. Use when the local-runtimes table points a job at…