cleanup

Audit Rust codebases for debug leftovers, dead code, and technical debt.

21|5|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/UnaMentis/pocket-tts-ios --skill cleanup-unamentis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleanup
Source: https://github.com/UnaMentis/pocket-tts-ios/tree/main/.claude/skills/cleanup
Command: npx skills add https://github.com/UnaMentis/pocket-tts-ios --skill cleanup-unamentis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and reports on code cruft, debug statements, and outdated documentation, helping to maintain a clean and efficient codebase.

Core Features & Use Cases

  • Debug Leftover Detection: Scans for println!, dbg!, and commented-out code.
  • Dead Code Identification: Flags unused imports, functions, and variables.
  • Documentation Audit: Checks for outdated READMEs, comments, and agent prompts.
  • Use Case: After a period of rapid development, run this Skill to ensure no debugging print statements or commented-out code blocks were accidentally committed, keeping the codebase production-ready.

Quick Start

Run the cleanup skill to audit the codebase for debug leftovers and technical debt.

Frequently Asked Questions about cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a Rust codebase for debug leftovers and technical debt?

To audit a Rust codebase for debug leftovers, run a scan to identify println!, dbg!, dead code, and outdated documentation, generating a structured report for review without modifying files.

What is the best way to find commented-out code and unused imports in Rust?

The best way to find commented-out code and unused imports in Rust is to use an auditing tool that scans the codebase for these specific patterns and flags them in a structured technical debt report.

Can I automatically remove dead code and debug statements during a codebase audit?

No, auditing a codebase for dead code and debug statements only identifies the issues and generates a report for human review; it does not automatically modify or remove any code from the files.

Does a Rust codebase audit check for outdated documentation and READMEs?

Yes, a Rust codebase audit checks for outdated documentation by scanning READMEs, comments, and agent prompts, flagging them alongside dead code and debug leftovers in the final technical debt report.

When should I scan for debug leftovers like println! and dbg! in my codebase?

You should scan for debug leftovers like println! and dbg! after a period of rapid development to ensure no debugging statements or commented-out code blocks were accidentally committed, keeping the codebase production-ready.