cleanup-audit
SolidWhole-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.
Install
Quality Score: 83/100
Skill Content
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
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.
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.
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.