Identify and verify unused TypeScript code artifacts before deletion.
npx skills add https://github.com/shift-editor/shift --skill dead-code-shift-editor
Please help me install this Agent Skill. Skill: dead-code Source: https://github.com/shift-editor/shift/tree/main/.claude/skills/dead-code Command: npx skills add https://github.com/shift-editor/shift --skill dead-code-shift-editor
Dead code detection often produces false positives that break builds or runtime behavior, especially when usage happens indirectly through interfaces and dependency-injection patterns.
Ask the skill to find and verify dead code by running the Knip candidate generators and then confirming each candidate with reference tracing and interface-contract checks before you remove anything.
High-intent search queries and answers about installing and using this skill.
Unused TypeScript code is safely removed by generating Knip candidates without auto-fixing, then verifying each candidate with AST-level reference tracing and interface contract validation before deletion. This prevents false positives that break builds.
Knip misclassifies interface-mediated class members as unused code because it cannot trace indirect usage through dependency injection and interface patterns. AST-level reference tracing resolves this by verifying interface contracts before any deletion.
The best way to clean up dead code is a verification-first workflow: run Knip to discover unused file, export, and class member candidates, then confirm or reject each candidate with AST analysis and interface tracing before removing anything.
No, using Knip --fix is forbidden because it auto-removes code without verification. You must manually verify each unused file, export, and class member candidate with AST-level reference checks and interface contract validation to avoid breaking builds.
During AST reference tracing, dead code removal candidates are categorized as confirmed dead, likely dead, or false positive. This risk-controlled workflow enforces verification and safety protocols before any code deletion occurs.
AST analysis is needed for dead code detection when your TypeScript project uses interfaces and dependency-injection patterns, because standard tools like Knip can produce false positives by failing to trace indirect usage through interface contracts.
endlessblinkDetect dead code and architectural issues in Vue 3 TypeScript monorepos.
DaccordProjectRun tests, fix lint errors, and remove debug artifacts from codebases.
johnlindquistConvert JavaScript to TypeScript with AST-guided renames and React hooks.
DayoptDetect and remove unused code, dead imports, and console statements in TypeScript/JavaScript projects.
