cleanup

Remove dead code, unused imports, and stale configuration files.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/g-zenr/relay-api --skill cleanup-g-zenr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleanup
Source: https://github.com/g-zenr/relay-api/tree/main/.claude/skills/cleanup
Command: npx skills add https://github.com/g-zenr/relay-api --skill cleanup-g-zenr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of identifying and removing dead code, unused imports, stale configuration, and other quality issues, leading to a cleaner, more maintainable codebase.

Core Features & Use Cases

  • Automated Code Hygiene: Scans and removes unused imports, functions, commented-out code, and empty files.
  • Configuration Management: Identifies and removes stale or inconsistent configuration entries.
  • Test File Cleanup: Streamlines test suites by removing empty test classes and unused fixtures.
  • Use Case: After a large feature merge, run /cleanup to automatically remove any code that is no longer necessary, ensuring the project remains lean and efficient.

Quick Start

Run the cleanup skill to remove dead code and fix import order.

Frequently Asked Questions about cleanup

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

FAQPage Schema
How do I automatically remove dead code and unused imports from my project?

Automated dead code removal scans your software project to delete unused imports, functions, commented-out code, and empty files. This process enforces import ordering and cleans test files to ensure your codebase remains maintainable and free of unnecessary clutter.

What is the best way to clean up stale configuration files after a large feature merge?

Cleaning up stale configuration files involves identifying and removing inconsistent or obsolete entries within your project. Running an automated cleanup after a large feature merge ensures any configuration that is no longer necessary is safely extracted and stripped away.

Do I need to run an audit before removing dead code and fixing import order?

Yes, an audit is required before removing dead code and fixing import order to safely identify unused functions and stale configuration. You must also verify that all tests and type checks pass post-cleanup to ensure the refactoring does not break existing functionality.

Can I streamline my test suites by removing empty test classes and unused fixtures?

Yes, test file cleanup streamlines your test suites by automatically removing empty test classes and unused fixtures. This automated code hygiene step reduces test maintenance overhead and ensures your testing environment remains lean and efficient.

What are the limitations of automating code hygiene and refactoring in a software project?

Automating code hygiene requires running an audit first and verifying that tests and type checks pass post-cleanup. Limitations include the necessity of passing these post-cleanup validation steps, meaning any broken tests will block the refactoring process until resolved manually.