What problem does it solve? TypeScript code often compiles green while hiding type-safety holes like unjustified any, unsafe as casts, non-null assertions, and loose tsconfig settings. This Skill performs a rigorous audit that treats types as proof of behavior, catching real risks instead of rubber-stamping a passing build. ## Core Features & Use Cases - Rule-Based Type Audit: Applies 16 defined rules covering no-any policy, unknown narrowing at boundaries, discriminated unions, exhaustiveness checks, branded types, and readonly data. - tsconfig Strictness Check: Verifies strict, noUncheckedIndexedAccess, exactOptionalPropertyTypes, and related flags, flagging missing ones as blockers. - Classified Findings Report: Outputs findings as Blocker, Strict, Improve, or Style with file:line citations and concrete fixes, saved to a persistent audit report path. - Use Case: Before merging a feature branch, run the audit on the diff against main to catch type-safety regressions and receive a saved report with a PASS / NEEDS WORK / BLOCKED verdict. ## Quick Start Ask the agent to run a TypeScript audit on the current branch diff or on specific files you name.