find-wasted-code
SolidUse ONLY when the operator runs "/find-wasted-code" (or explicitly asks to "scan the repo for dead-end tool calls / broken links / missing helpers / footgun configs / silent push-through"). Statically scans THIS repo for friction footguns and writes a tracked report to docs/wasted-code/report.md. Manual-trigger ONLY — do NOT auto-invoke; the skill carries disable-model-invocation and no hook wires it. Read-only except the one report write. Findings are review candidates, never auto-fixes. Do NOT use for token/transcript economy (/token-waste-audit), for process ceremony (/find-wasted-effort), or for CLI/Flow drift health (/fusebase-health).
Install
Quality Score: 83/100
Skill Content
Details
- Author
- fusebase-dev
- Repository
- fusebase-dev/fusebase-flow
- Created
- 4 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
cleanup-audit
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.
audit
Use when auditing, reviewing, hardening, or assessing code — a whole codebase, a single module, a branch diff, staged changes, or a PR. Triggers include 'audit', 'code review', 'security review', 'find vulnerabilities', 'check for weaknesses', 'is this code safe', 'pre-release review', 'what could go wrong here', 'quality review', 'this is getting messy', 'improve the architecture', 'find refactoring opportunities', 'is this abstraction worth it'. Any language, any layer: backend, frontend, CLI, library, infrastructure-as-code. Defensive purpose only: findings and remediation, never exploit development.
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.