cleanup

Name: cleanup
Availability: InStock
Author: whatsper

Identify unused code, orphaned assets, and stale exports in TypeScript/JavaScript projects.

1|Updated Jul 17, 2025

Search Tags:#code quality #static analysis #codebase #cleanup #refactor #dead code

Ready to run

npx skills add https://github.com/whatsper/texterdocs --skill cleanup-whatsper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleanup
Source: https://github.com/whatsper/texterdocs/tree/main/.claude/skills/cleanup
Command: npx skills add https://github.com/whatsper/texterdocs --skill cleanup-whatsper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify leftover dead code, orphaned files, stale CSS/exports, and other cruft that accumulate after changes, so you can surface these issues for cleanup.

Core Features & Use Cases

Ground truth establishment by scanning codebases, package configs, and project structures to distinguish live and dead items.
Detect unused exports, unreachable code, stale assets, and unreferenced resources, with clear reports for remediation.
Use cases include cleaning up after refactors, preparing for audits, or simplifying a large monorepo.

Quick Start

Run a full scan of your project to surface dead code, unused assets, and stale exports.

Frequently Asked Questions about cleanup

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

FAQPage Schema

How do I find unused exports and dead code in a large TypeScript monorepo?▼

To find unused exports and dead code in a TypeScript monorepo, scan the codebase using project metadata from package.json and tsconfig. This establishes ground truth to distinguish live items from orphaned assets and stale exports for a reliable cleanup report.

Can I scope dead code detection to specific folders in a JavaScript project?▼

Yes, you can scope dead code detection to specific folders in a JavaScript project. The scanning process supports scoping to target directories, allowing you to isolate and report unused code and unreferenced resources within particular areas of your codebase.

What is the best way to identify orphaned assets and stale CSS after refactoring?▼

The best way to identify orphaned assets and stale CSS after refactoring is to run a full codebase scan. This compares project structures and package configs to detect unreferenced resources, unreachable code, and stale exports for remediation.

Do I need to provide package.json and tsconfig files to detect unreachable code?▼

Yes, you need to provide package.json and tsconfig files to detect unreachable code accurately. These project metadata files are required to determine live versus dead code and produce a reliable report across your frameworks.

Does static analysis for dead code work with Docusaurus configurations?▼

Yes, static analysis for dead code works with Docusaurus configurations. The scanning process requires Docusaurus config alongside package.json and tsconfig settings to establish ground truth and accurately identify stale assets and unused exports.

What are the limitations of cleaning up dead code in legacy codebases?▼

A limitation of cleaning up dead code in legacy codebases is the reliance on accurate project metadata. Without correct package.json, Docusaurus config, and tsconfig settings, the tool cannot reliably distinguish live code from dead code across complex monorepos.