Identify unused code, orphaned assets, and stale exports in TypeScript/JavaScript projects.
npx skills add https://github.com/whatsper/texterdocs --skill cleanup-whatsper
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
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.
Run a full scan of your project to surface dead code, unused assets, and stale exports.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
TakazudoRender creation date, last updated date, and author under H1 titles in Docusaurus v3.x pages.
maggitDetect and remove dead, unused, or unreachable code across codebases.
vertivolatamRun static analysis across multiple programming languages with linters and security scanners.
OmicoExecute Gradle dependency checks and extract resolved versions from dependency-tree outputs.
