repo-cleanup-auditor

Repo Cleanup Auditor

Use this skill for repo hygiene work where the first step should be a broad scan and a human approval checkpoint.

Core Rule

Do not move, delete, or rename anything during the first pass. First produce a cleanup audit. Apply changes only after the user explicitly approves specific actions.

If the user already approved a specific cleanup action, you may execute that action, but still inspect references and validate afterward.

First Pass: Repo Scan

Start at the repo root. If you are not sure which directory is the repo root, run git rev-parse --show-toplevel.

Inspect:

git status --short --untracked-files=all
rg --files
find . -maxdepth 3 -type d | sort
find . -maxdepth 4 -type f -empty | sort

Then use rg to check references before recommending a move, rename, or deletion. For large or binary-heavy repos, avoid exhaustive reads; sample names, manifests, READMEs, scripts, and tracked file lists first.

Classification

Classify findings into exactly these sections, in this order.

Potential Deletions

Possibly obsolete, generated, stale, duplicated, or confusing files where the evidence is not strong enough to delete without human judgment.

Use this table:

ID	Path	Why suspicious	Evidence	Risk if deleted	Suggested action

STRONG Candidates for Deletion

High-confidence clutter: empty folders, .DS_Store, stale generated outputs, duplicate rollups, outdated snapshots, abandoned scratch files, local temp artifacts, superseded outputs with a clearer canonical copy, or files with no references and obvious generated naming.

Use this table:

ID	Path	Why strong	Evidence	Risk if deleted	Exact delete command

Potential Moves

Files or folders that likely belong somewhere else, but where the destination needs human judgment.

Use this table:

ID	Path	Current problem	Possible destination	Reason	Risk