AgentSkillsCN

s-clean

查找并删除死代码和过时文档。涵盖未使用的函数、孤立文件、无效链接和过时引用。用于维护、发布前清理或代码库卫生。触发词：清理、死代码、未使用、孤立、过时、垃圾、维护。

SKILL.md
--- frontmatter
name: s-clean
description: >
  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 - Cleanup workflow
  • •c-review - Full review (includes clean step)

MCP Tools

TaskMCP Tool
Find Dead Codeaddon.deadcode(addon="MyAddon")
Find Stale Docsdocs.stale(addon="MyAddon")
Filter by Confidenceaddon.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)

CategoryDescription
unused_functionFunctions defined but never called
orphaned_fileLua files not in TOC
dead_exportExported values never used
unused_libraryLibraries in Libs/ never used
stale_eventEvent handlers for unregistered events
commented_codeLarge blocks of commented-out code

Stale Docs (docs.stale)

CategoryDescription
dead_linkInternal links to non-existent files
dead_referenceMentions of functions/files that don't exist
version_driftOld version numbers in documentation
relative_stalenessDocs 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

LevelMeaningAction
Definite100% certain (e.g., file not in TOC)Safe to remove
Likely90%+ certain (e.g., function never called)Review briefly, usually safe
Suspicious70%+ 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