v1.0.0
Enforces strict TypeScript practices — proper generics, discriminated unions, exhaustive checks, and elimination of any. Weak types propagate silently through a codebase, so this skill catches the patterns that erode type safety before they spread.
A review skill that ensures your TypeScript code delivers on its promise of type safety rather than just adding syntax overhead.
Run this on any TypeScript project, particularly after adding new modules or when reviewers frequently catch type-related issues. Essential for shared libraries where consumers depend on accurate types.
Enable all strict flags in tsconfig.json (strict: true). Without strict mode, TypeScript allows null access, implicit any, and unchecked function calls that will crash at runtime.
Never use `any` as a type annotation. `any` disables all type checking for that value and everything it touches, spreading through your codebase like a virus — one `any` can silently disable type safety across dozens of files.
Model mutually exclusive states with discriminated unions, not optional fields. Optional fields allow impossible states (e.g., `status: 'success'` with `error: 'failed'`) that compile but crash at runtime.
Use `unknown` instead of `any` for values with uncertain types. Unlike `any`, `unknown` forces you to narrow the type before using it, keeping type safety intact.
Avoid `as Type` assertions — they tell TypeScript "trust me" and skip validation. If the runtime value doesn't match, your code crashes with no type error to warn you.
BeforeMerge scans your pull requests against all 5 TypeScript Review rules automatically. Get actionable feedback before code ships.