After your code passes review, it needs a final polish. This skill removes debug logs, temporary comments, and dead code. It also optimizes imports and improves readability. The code stays the same but looks much cleaner. This makes it ready for production.
Developers use this skill to tidy up after changes are approved. It is not for changing how the code works. It only cleans up the mess left behind during development. The result is a neat and professional codebase.
Global
mkdir -p ~/.claude/skills/specs-code-cleanupProject
mkdir -p .claude/skills/specs-code-cleanupSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Reviewmattpocock/skills
Check code against standards and spec in one review