cleanup

You can identify unused npm packages by running dependency analysis tools that scan your package.json and codebase. Dependency pruning removes bloated packages to reduce bundle size and ensure a production-ready environment.

Yes, you can safely remove unused imports and variables by integrating with static analysis tools like ts-prune, depcheck, and unimported. These tools map code usage to ensure safe removal of dead code without breaking functionality.

The best way to audit frontend code is to run a cleanup skill that consolidates duplicate logic and removes debug statements like console.log. This code quality audit ensures your codebase remains production-ready and maintainable.

Dead code elimination works across both JavaScript and TypeScript files to detect and remove unused imports, variables, and commented-out code. It operates throughout the frontend project to prune redundant logic effectively.

Yes, you need static analysis tools such as ts-prune, depcheck, or unimported to execute a code quality audit. Integration with these dependencies is required to ensure safe removal of dead code and unused assets.