cleanup
From the author
Reclaim disk space and prune branches left behind by AI coding agents - merged or abandoned git worktrees, merged branches, stale build artifacts (node_modules, .venv, target), old archives and backups, package caches, and old agent session logs. Use when the user runs /cleanup, says the disk is full, or asks to clean up worktrees, branches, or storage.
Install
npx skills add davepoon/buildwithclaude --skill cleanup -a claude-code
Installs to .claude/skills/cleanup/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 84
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- git-cleanupOutlineDriven/outline-driven-developmentUse when the user explicitly invokes branch or worktree cleanup for a repo with accumulated local branches. Don't use for remote branch deletion or force-push operations.Engineering★ 54
- ai-git-cleanuparcasilesgroup/ai-engineeringRemoves finished local git work in one automatic pass, with no question and no name to type: dead worktrees first (`git worktree remove`, then `git worktree prune`), then branches already merged into the local `main`, then the branches a squash-merged pull request left behind (tree identical to `origin/main`, tagged before deletion). Trigger for "tidy up", "tidy up these branches", "tidy branches", "delete old branches", "start fresh", "limpieza de branches", "limpia branches", or by naming ai-git-cleanup. A branch that is not merged into `main` is left alone — unless its tree is byte-identical to `origin/main`, which is what a squash-merged pull request looks like afterward; the pass deletes those with the proof in hand, tags the tip, and never force-deletes anything else. Not for pushing, not for remote branches, not for opening a pull request.Engineering★ 61
- git-branch-cleanupgotalab/skillportAnalyzes and safely cleans up local Git branches. Categorizes branches by merge status, staleness, and remote tracking. Provides interactive selection with safety guards. Use when the user wants to clean up branches, delete old branches, organize Git branches, or asks about which branches can be safely deleted.Engineering★ 418
- clean-clean-cutOutlineDriven/outline-driven-developmentUse when asked to run /clean-clean-cut to cut accumulated records and residue. Not for untracked or non-VCS changes, or branch/worktree cleanup: use git-cleanup.Engineering★ 54
- repo-cleanupNickCrew/Claude-CortexUse when a repository needs cleanup of dead code, build artifacts, unused dependencies, outdated docs, or stale tests - provides safe cleanup workflows, validation steps, and reporting templates for code, deps, docs, tests, and sprint archives.Testing★ 61
- tidy-branchesGoldziher/ai-rulezCleans up stale git branches. Use when the repository has many merged branches.Engineering★ 163
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in