cleanup-audit

Solid

Whole-repo audit for over-engineering and accidental complexity. Scans the entire codebase (not just a diff) and returns a ranked, read-only list of what to delete, simplify, or replace with standard-library or platform equivalents. Use when the user asks to "audit the codebase", "find bloat", "what can I delete", or wants a repo-wide simplification pass. For a diff-scoped pass use `pythinker review diff --mode deslopify` instead. One-shot report; applies no fixes.

Code & Development 27 stars 8 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
48
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Cleanup Audit A read-only, whole-repo pass that hunts accidental complexity and over-engineering. The diff-scoped version of this job already ships as `pythinker review diff --mode deslopify`; this skill is its repo-wide complement — scan the whole tree, rank the biggest cut first. Scope is complexity only. Correctness bugs, security holes, and performance belong to a normal review or security pass — note them in one line if you trip over them, but do not chase them here. ## What to hunt - Dead code, unused flexibility, and speculative features no caller needs. - Hand-rolled logic the standard library already ships — name the function that replaces it. - A dependency (or hand-written code) doing what the language, runtime, or framework already does. - Single-implementation interfaces, one-product factories, wrappers that only delegate, a module that exports one trivial thing, dead flags and config nobody sets. - The same logic spelled out long-hand where a shorter, equally clear form exists. ## How to work 1. Map before judging: read the tree, the manifest/lockfile, and entry points; use `Grep`/`Glob` (or `LSP` for references and call hierarchy) to confirm a thing is actually unused before proposing its deletion. A deletion proposed without checking callers is a guess. 2. Rank findings biggest cut first. 3. Apply nothing. This is a report. ## Output One line per finding, ranked, each tagged and citing a path: - `delete:` — dead code / speculative feature. R...

Details

Author
Pythoughts-labs
Repository
Pythoughts-labs/pythinker-code
Created
4 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

audit

Audit a whole repo or module for over-engineering that is alive and in use — speculative generality, pass-through layers, frameworks where a function would do, homegrown versions of stdlib features — and hand back a delete-list with evidence. Use on /1337:audit, or when the user asks whether the codebase is over-built, what can be simplified repo-wide, or says a codebase feels bloated or over-abstracted. Read-only; never edits. Diff-scoped review → /1337:review; dead code and markers → /1337:debt.

0 Updated today
dimitritholen
Code & Development Listed

complexity-audit

Scan an entire codebase (or a chosen subtree) for over-engineering — premature abstraction, speculative generality, needless layering, wrapper-only modules, dead config/flags, indirection without payoff — and return a prioritized, deletion-oriented report. Use for "audit complexity", "find over-engineering", "where are we over-built", "complexity-audit". Complements the per-diff /code-review and /simplify (which look at the current change); this looks at the whole tree. Aligned to the persona's anti-pattern list.

1 Updated 3 weeks ago
yuri-semenenko
Code & Development Listed

lean-code-review

Review a code diff or, when explicitly requested, a whole repository for unnecessary complexity: dead flexibility, duplicated helpers, speculative abstractions, avoidable dependencies, hand-written stdlib/platform features, wrappers that only delegate, and code that can be safely deleted or inlined. Use when the user asks for an over-engineering review, lean review, deletion pass, simplification audit, bloat audit, YAGNI review, or asks what code or dependencies can be removed. Return evidence-backed findings only; do not apply fixes unless asked. This complements correctness, security, performance, and accessibility review rather than replacing them.

0 Updated today
ongkipro