unused-code-cleanup

Remove unused code by enabling TypeScript's --noUnusedLocals and --noUnusedParameters compiler flags, then systematically delete unused imports, variables, and parameters flagged as TS6133 errors. Verify with a build to confirm zero warnings and a clean production bundle.

Identify dead code by running `npx tsc --noEmit --noUnusedLocals --noUnusedParameters` to surface unused imports, props, and local variables across components, hooks, and utilities. Prioritize high-impact files and verify changes with tests and builds.

Yes. Systematically detect unused imports, variables, and parameters across large codebases using TypeScript compiler flags. Process files in priority order, verify each batch with builds and tests, and track progress toward eliminating all TS6133 warnings.

Removing unused code reduces bundle size, eliminates compiler warnings, and improves build health. It's essential during refactors and pre-production cleanup to ensure runtime performance and a warning-free TypeScript configuration.

Yes. You need a TypeScript configuration file with --noUnusedLocals and --noUnusedParameters enabled to detect unused code. Build verification is required afterward to confirm zero warnings and validate the clean production bundle.

TypeScript flags unused imports, unused local variables, unused function parameters, and unused props in components. The skill also handles removal of debug snapshots and other dead code patterns across components, hooks, utilities, and API layers.