cleanup-enforcement

Remove dead code, unused imports, and progress comments from TypeScript and Go projects.

Updated Aug 23, 2026

Search Tags:#typescript #golang #cleanup #refactor #lint #dead-code #legacy-cruft

Ready to run

npx skills add https://github.com/DaichiHoshina/ai-tools --skill cleanup-enforcement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleanup-enforcement
Source: https://github.com/DaichiHoshina/ai-tools/tree/main/claude-code/skills/cleanup-enforcement
Command: npx skills add https://github.com/DaichiHoshina/ai-tools --skill cleanup-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces strict cleanup by removing dead code, unused imports, and progress comments to maintain a clean codebase and prevent legacy cruft from creeping back.

Core Features & Use Cases

Remove unused imports, variables, constants, functions, and types in TypeScript and Go projects.
Prohibit forward-compatibility cruft such as deprecated exports and legacy re-exports.
Enforce removal of progress and status comments to keep codebase concise and focused.
Generates a cleanup report summarizing deletions and remaining hotspots for review.

Quick Start

Invoke the cleanup-enforcement process during development or after refactors to ensure code cleanliness before merging.

Frequently Asked Questions about cleanup-enforcement

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

FAQPage Schema

How do I remove dead code and unused imports from TypeScript and Go projects?▼

To remove dead code, scan for unused imports, variables, constants, functions, and types during development or refactoring. A cleanup summary is generated to report deleted items and remaining hotspots for review.

What is legacy cruft and how do I prevent it from creeping back into my codebase?▼

Legacy cruft includes deprecated exports and legacy re-exports. Prevent it from creeping back by enforcing strict cleanup rules during development and code reviews to prohibit forward-compatibility cruft and maintain a clean codebase.

When should I enforce cleanup to remove progress comments and dead code?▼

Enforce cleanup during the development, refactoring, and code review phases to ensure code cleanliness before merging. This prevents progress and status comments from accumulating and keeps the codebase concise and focused.

Can I use cleanup enforcement to identify remaining hotspots in a TypeScript project?▼

Yes, cleanup enforcement generates a cleanup report summarizing deleted items and remaining hotspots in TypeScript and Go projects. This report highlights areas requiring further review after removing dead code and unused imports.

Does cleanup enforcement work with both TypeScript and Go for removing unused variables?▼

Yes, cleanup enforcement works with both TypeScript and Go projects to identify and remove unused variables, constants, functions, and types, ensuring a clean codebase across both languages.