reviewing-type-safety

Type-safety detection identifies unsafe patterns like unguarded any usage, unsafe assertions, and missing type guards across your codebase. The Skill scans API handlers, parsers, and data models during code reviews, flagging violations with file paths and line numbers to guide fixes.

A comprehensive review detects no-any violations, missing runtime validation at boundaries, weak type guards, missing generic constraints, and unsafe type assertions. It ensures type policies remain consistent across modules and API surfaces.

Yes. The Skill applies cross-project consistency checks as a cross-cutting review plugin, validating type safety uniformly across all API handlers, parsers, and data models in your codebase to enforce aligned type policies.

Runtime validation is enforced at data entry points using schemas and type guards. The Skill identifies missing runtime checks at boundaries and recommends concrete type refinements and discriminated unions to strengthen guarantees.

Static type checking catches compile-time errors. Type-safety code review goes further, detecting unsafe patterns the compiler allows—unguarded any, missing guards, and weak assertions—that pose runtime risks during actual data flow.

Run audits during code reviews, especially when changes touch API handlers, data parsers, or domain models. Use it to enforce no-any policies, validate schema-backed boundaries, and prevent type safety regressions across your project.