skills.rest
DaichiHoshina
DaichiHoshinaCOMMUNITY
Explore all skills by this author →
𝕏@last_resort_dhGitHub

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
One-click install
npx skills add https://github.com/DaichiHoshina/ai-tools --skill cleanup-enforcement
Or copy as Structured Prompt for Agent▼
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.

Related Skills

Explore More Software Engineering Skills→
peancharoenpeancharoen

speckit.checker

Run static analysis tools to detect linting, type, and security issues across source code.

Community
Advanced
alfredolopez80alfredolopez80
145

deslop

Remove AI-generated comments, defensive checks, and casts from code branches.

Community
Intermediate
timurgaleevtimurgaleev
5

health

Aggregate test outcomes, lint warnings, and dead code signals into a single health score.

Community
Advanced
wildbitcawildbitca
1

code-cleanup

Remove dead code, unused imports, and empty directories across multiple languages.

Official
Advanced