remove-ts-nocheck-from-legacy

To remove @ts-nocheck from legacy TypeScript files, this Skill refactors the code by deleting the suppression directive and adding proper type annotations. It extracts type definitions into separate modules to improve code maintainability.

Adding type annotations to legacy TypeScript code is best handled by extracting type definitions into separate modules and importing them. This Skill transforms files by identifying concerns and applying proper types with minimal file I/O changes.

Yes, you can refactor large TypeScript files where @ts-nocheck has been used to suppress errors. This process safely removes the directive and introduces proper type annotations needed for robust future development.

Yes, automating the removal of @ts-nocheck and extraction of types assumes a basic understanding of TypeScript and refactoring techniques. This prerequisite knowledge helps you manage the newly introduced type annotations effectively.

Removing @ts-nocheck requires extracting helper functions to properly isolate concerns and define types without breaking existing logic. This refactoring approach ensures the newly added type annotations integrate cleanly into separate modules.