Loading...
Loading...
Found 37 Skills
Use when scanning for and cleaning up code slop — duplicate patterns, dead code, misplaced files, and accidentally committed files.
Automate lifecycle checks for migration code (TODO(migration)). Detect expired or insufficiently documented migration code and output results in report format. It is used for checking remaining TODO(migration) entries in the codebase, cleaning up expired migration code, and taking inventory of technical debt. This is a mechanism to prevent leaving "to be deleted later" code unattended.
Local-first code intelligence — structural search, symbol context, impact analysis, and dead code detection via typed graph traversal. Use this skill when you need to search a codebase by intent (not just substring), understand how symbols connect, trace change impact before refactoring, find dead code, or get an architecture briefing. Triggers on: search codebase, find symbol, who calls, blast radius, impact analysis, dead code, code graph, structural search, architecture overview, codebase orientation, understand connections, what depends on, find where.
Audit a codebase for dead code, unreachable branches, duplicated logic, and vestigial abstractions, then remove them safely with proof. Use to reduce sprawl, pay down tech debt, or clean up after a feature is retired or migrated.
Ships the smallest thing that does the job and deletes what nobody asked for.
Finds unused dependencies, files, and exports in JS/TS projects. Use when cleaning up dead code, removing stale packages from package.json, or identifying unreferenced exports.
Systematic tech debt inventory with complexity analysis, dead code detection, and remediation planning. Track debt over time. NOT for code review (review) or refactoring.
Simplifies, polishes, and declutters code without changing behavior. Use when asked to simplify, clean up, refactor, declutter, remove dead code or AI slop, or improve readability. For analysis-only reports without code changes, use code-simplicity-reviewer agent.
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
Clean up code, remove dead code, and optimize project structure. Use when user wants to clean codebase, remove unused code, or optimize imports.
Refactor and simplify settled, recently modified code to improve readability, remove dead branches, flatten deeply nested logic, and reduce duplication while preserving behavior. Use when cleaning up complex functions, eliminating boilerplate, deduplicating logic, or improving code altitude after tests pass — even if the user does not explicitly say "fable-simplify" (e.g. "simplify this code", "clean up this function", "refactor this logic", "make this cleaner"). Do NOT use when tests are failing (use fable-recover) or for speculative architectural rewrites (use fable-plan).
Find evidence-backed simplifications in DeepSeek Harness code, APIs, configuration, tests, and prose; write or consolidate proposals, identify small inline cleanups, or assess simplifications from another branch. Use for removing dead, duplicated, speculative, or unnecessarily maintained behavior and infrastructure.