How do I install the S Clean skill?

Run npx skillmds add majiayu000/s-clean in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is S Clean safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with S Clean?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is S Clean free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published S Clean?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

S Clean by majiayu000 — Agent Skill

Name: S Clean
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

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.

majiayu000 57deb36 2 files · 3.2 KB Updated Sep 9, 2026 567 repo stars

File contents

Cleaning WoW Addons

Expert guidance for finding and removing cruft in addon codebases.

Related Commands

c-clean - Cleanup workflow
c-review - Full review (includes clean step)

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.deadcode with include_suspicious=false for high-confidence issues only
Remove identified dead code
Run docs.stale to find documentation issues
Fix broken links and update outdated references

Deep Cleanup

Run addon.deadcode with all confidence levels
Manually verify suspicious findings before removal
Run docs.stale with 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, loadstring may hide usage
Preserve intentional dead code — Mark with -- KEEP: comment if needed
Update docs after code changes — Run docs.stale after refactoring

---name: s-cleandescription: 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.--- # Cleaning WoW Addons Expert guidance for finding and removing cruft in addon codebases. ## Related Commands - [c-clean](../../commands/c-clean.md) - Cleanup workflow - [c-review](../../commands/c-review.md) - Full review (includes clean step) ## 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 1. **Dead Code Detection** — Find unused functions, orphaned files, dead exports 2. **Stale Docs Detection** — Find broken links, outdated refs, version drift 3. **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 1. Run `addon.deadcode` with `include_suspicious=false` for high-confidence issues only 2. Remove identified dead code 3. Run `docs.stale` to find documentation issues 4. Fix broken links and update outdated references ### Deep Cleanup 1. Run `addon.deadcode` with all confidence levels 2. Manually verify suspicious findings before removal 3. Run `docs.stale` with all techniques 4. 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 1. **Start with definite issues** — These are safe to fix immediately 2. **Check dynamic patterns** — `_G`, `rawget`, `loadstring` may hide usage 3. **Preserve intentional dead code** — Mark with `-- KEEP:` comment if needed 4. **Update docs after code changes** — Run `docs.stale` after refactoring

Frequently asked questions