Skill

code-cleanup

Use when asked to clean up code, or after introducing a new larger feature. Identifies bad patterns, fix warnings.

Stars

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/superpowers:code-cleanup

User invocable

Model invocable

Inline context

Default effort

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

- Run the appropriate compilation and/or other existing code-quality tools (linting, credo, etc)

29 lines · ~347 tokens

Stats

LanguageShell

Stars1

MaintenancePoor

Last CommitMar 18, 2026

Actions

Stats

Actions

Run the appropriate compilation and/or other existing code-quality tools (linting, credo, etc)
- for js: run pnpx knip
- for elixir: run mix credo - add it if it's not available
Rate all warnings/issues based on their complexity.
Group related issues into Batch-Tasks. For example all "prefix unused var with _" in a single task
Then check if there's an appropriate Agent to review the existing code.
On large code-bases spawn the language expert agents in parallel to handle single large files or folders of smaller files.
Create a CLEANUP.md to record your findings and suggestions.
Ask the user how to review that cleanup.md plan.
Run tests before making changes to assess the state of the test suite
If there are failing tests, ask the user whether to investigate those in the cleanup as well, or if they should be ignored.
If the user approves of the CLEANUP.md, spawn agents in parallel for tasks that can be done in parallel and don't interfere with each other.
Run the test suite again (or the subset of succeeding tests, or ignore if user said so)

Follow idiomatic coding guidelines and refer to other skills/agents whenever possible and/or necessary.