worktree-cleanup
Audit Git worktrees and reclaim confirmed-unused checkouts without losing local work. Use when asked to clean stale worktrees or recover disk space.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- worktree-cleanup
- metadata
- { "author": "Brenden Bishop", "attribution": "../../ATTRIBUTION.md" }
- description
- Audit Git worktrees and reclaim confirmed-unused checkouts without losing local work. Use when asked to clean stale worktrees or recover disk space.
02 资源文件 1
- 脚本scripts/audit.py2.5 KB
03 SKILL.md 正文
Worktree cleanup
Run the bundled read-only audit for the repository. It lists Git worktrees and checks branch, local changes, ignored files, and unpushed commits. It does not declare a checkout safe to delete. Compare candidates with active agent sessions, pinned chats, running processes, and any worktree attachments the host exposes. A missing transcript is unknown usage, not proof that nobody needs the worktree.
Show the exact paths proposed for removal and why. Keep the primary checkout, active sessions, dirty worktrees, unpushed commits, and uncertain candidates. Before deletion, obtain approval for the exact paths. Use git worktree remove without --force on confirmed clean paths; verify Git's list afterward. Never use rm -rf as a fallback for a failed worktree removal. Do not delete simulators, caches, or unrelated directories as part of this skill.
04 同仓库更多 Skills
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing. Must always apply.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.