s-clean
Find and remove dead code and stale documentation. Covers unused functions, orphaned files, dead links, and outdated references. Use for maintenance, pre-release cleanup, or codebase hygiene. Triggers: clean, dead code, unused, orphan, stale, cruft, maintenance.
When & Why to Use This Skill
The s-clean Claude skill is a powerful codebase maintenance utility designed to automate the detection and removal of technical debt. It specializes in identifying dead code, such as unused functions and orphaned files, while also auditing documentation for stale references and broken links. By providing confidence-based reporting, it helps developers maintain high code hygiene and streamline pre-release cleanup workflows.
Use Cases
- Pre-release Cleanup: Automatically identify and remove unused functions, orphaned Lua files, and commented-out code blocks before shipping a release to ensure a lean codebase.
- Legacy Code Refactoring: Scan large or aging repositories to find 'dead' exports and unused libraries that are no longer necessary, reducing project complexity.
- Documentation Maintenance: Detect broken internal links, outdated version numbers, and stale references in READMEs or technical docs to ensure documentation stays in sync with the code.
- Code Hygiene Audits: Perform regular health checks to find stale event handlers or orphaned files not included in the TOC (Table of Contents), preventing 'cruft' accumulation.
| name | s-clean |
|---|---|
| description | > |
| Triggers | clean, dead code, unused, orphan, stale, cruft, maintenance. |
Cleaning WoW Addons
Expert guidance for finding and removing cruft in addon codebases.
Related Commands
MCP Tools
| Task | MCP Tool |
|---|---|
| Find Dead Code | addon.deadcode(addon="MyAddon") |
| Find Stale Docs | docs.stale(addon="MyAddon") |
| Filter by Confidence | addon.deadcode(addon="MyAddon", include_suspicious=false) |
Capabilities
- Dead Code Detection — Find unused functions, orphaned files, dead exports
- Stale Docs Detection — Find broken links, outdated refs, version drift
- Confidence Levels — Definite (100%), Likely (90%+), Suspicious (70%+)
Detection Categories
Dead Code (addon.deadcode)
| Category | Description |
|---|---|
unused_function |
Functions defined but never called |
orphaned_file |
Lua files not in TOC |
dead_export |
Exported values never used |
unused_library |
Libraries in Libs/ never used |
stale_event |
Event handlers for unregistered events |
commented_code |
Large blocks of commented-out code |
Stale Docs (docs.stale)
| Category | Description |
|---|---|
dead_link |
Internal links to non-existent files |
dead_reference |
Mentions of functions/files that don't exist |
version_drift |
Old version numbers in documentation |
relative_staleness |
Docs not updated in many commits |
Workflow
Quick Cleanup
- Run
addon.deadcodewithinclude_suspicious=falsefor high-confidence issues only - Remove identified dead code
- Run
docs.staleto find documentation issues - Fix broken links and update outdated references
Deep Cleanup
- Run
addon.deadcodewith all confidence levels - Manually verify suspicious findings before removal
- Run
docs.stalewith all techniques - Update documentation to match current code
Confidence Interpretation
| Level | Meaning | Action |
|---|---|---|
| Definite | 100% certain (e.g., file not in TOC) | Safe to remove |
| Likely | 90%+ certain (e.g., function never called) | Review briefly, usually safe |
| Suspicious | 70%+ certain (e.g., dynamic code patterns) | Manual verification required |
Best Practices
- Start with definite issues — These are safe to fix immediately
- Check dynamic patterns —
_G,rawget,loadstringmay hide usage - Preserve intentional dead code — Mark with
-- KEEP:comment if needed - Update docs after code changes — Run
docs.staleafter refactoring