refactor-clean

Invoke this Skill with the target file or directory, and the assistant will scan for unused functions, variables, and unreachable branches, then propose or apply removals. Review the suggested changes before committing to ensure nothing referenced dynamically is deleted.

The Skill identifies repeated logic across files and merges it into a single shared implementation, updating call sites accordingly. Provide the scope you want analyzed, such as a module or package, to keep the consolidation focused.

Dead code removal is generally safe for statically referenced code, but reflection, dynamic imports, or string-based lookups can create hidden usages. Always run your test suite after cleanup and review deletions involving public APIs or entry points.

Avoid running it right before a release or on code with incomplete test coverage, since subtle behavioral changes may go unnoticed. It works best on well-tested modules where deletions and consolidations can be verified quickly.