type-checker

Type checking identifies mismatched types, missing definitions, and unsafe `any` usage. Run `npm run typecheck` to detect errors, then apply fixes by defining proper types, replacing `any` with specific types, or updating interface annotations until all errors resolve.

Yes. This Skill reads type-check error outputs—file paths, line numbers, error codes, and messages—then proposes or applies repairs by using existing types, defining new ones, or applying generics, verifying fixes by re-running `npm run typecheck`.

Run type checking to capture errors, interpret the error messages and affected lines, decide whether to use an existing type, create a new one, or apply generics, modify the code, then re-run `npm run typecheck` to confirm all issues are resolved.

Type checking and fixing applies to both frontend and backend TypeScript projects. The process reads errors, accesses type definitions, applies repair strategies, and verifies results uniformly across any codebase using strict typing.

Replacing `any` enforces strict type safety by catching errors at compile time rather than runtime. Strong typing prevents silent bugs, improves code maintainability, and enables better tooling support like autocomplete and refactoring.

Ignoring type errors leaves unsafe code that fails at runtime; fixing them enforces compile-time safety. Addressing errors through proper types, definitions, or generics prevents bugs, improves code clarity, and strengthens overall codebase reliability.