typescript-type-system-review

Reviews TypeScript code for type safety, API contracts, generics, and invalid state modeling.

2|Updated May 6, 2026
One-click install
npx skills add https://github.com/bpcakes/jig-skills --skill typescript-type-system-review-bpcakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-type-system-review
Source: https://github.com/bpcakes/jig-skills/tree/main/plugins/jig-typescript/skills/typescript-type-system-review
Command: npx skills add https://github.com/bpcakes/jig-skills --skill typescript-type-system-review-bpcakes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? TypeScript codebases often accumulate unsafe casts, untyped boundaries, and weak state modeling that let runtime errors slip past the compiler. This Skill performs a focused review of type-system usage so defects are caught with evidence rather than linter-style noise. ## Core Features & Use Cases - Type Safety Audit: Investigates any, type assertions, non-null assertions, and unvalidated runtime values, tracing concrete consequences before reporting. - API and Contract Review: Examines exported types, function signatures, component props, and service interfaces for leaked implementation details and representable invalid states. - Generics and Utility Types: Flags unnecessary generics, weak constraints, and misuse of Partial, Pick, Omit, Record, and similar utility types. - Use Case: After refactoring a TypeScript service layer, run this review on the working changes to receive severity-ranked findings with locations, counterevidence analysis, and suggested fixes, plus an overall type-system health rating. ## Quick Start Ask the agent to review your current working changes for TypeScript type safety and report findings with file locations without editing code.

Frequently Asked Questions about typescript-type-system-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review TypeScript code for type safety issues?

Run this review against your current working changes, a feature branch, or named files. It investigates any usage, type assertions, non-null assertions, and unvalidated runtime values, then reports severity-ranked findings with locations and suggested fixes.

What does a TypeScript type system review check?

It checks type safety, type clarity, inference versus explicit annotations, interface and type usage, generics, utility types like Partial and Omit, and API design. It also flags boolean flags that should be discriminated unions and APIs that make invalid states representable.

Does this review edit my TypeScript code automatically?

No, it reports findings without editing code unless you explicitly ask for fixes. Review-only requests produce a report with severity, location, counterevidence considered, and suggested fixes.

Can it review only specific files or a branch instead of all changes?

Yes. By default it inspects git diff for working changes, but you can scope it to a feature branch comparison against the merge base, a base ref, or explicitly named files and directories.

How is this different from running ESLint or the TypeScript compiler?

It ignores superficial formatting and requires tracing a concrete consequence before reporting a defect. It also recommends compiler settings like strict, noUncheckedIndexedAccess, and exactOptionalPropertyTypes when they would materially improve safety.