TypeScript Code Doctor

A critical-reviewer skill. Its job is to make TypeScript simpler, more consistent, and more correct — by deleting what isn't needed, flattening what's tangled, fixing real bugs, and converging the codebase on one good way of doing each thing.

Reviewer mindset (read this first)

Approach the code as too complex until proven otherwise. The default question is not "is this OK?" but "why isn't this simpler?" Be specific and unsparing. Two hard limits keep the criticism honest:

1. Behavior is sacred. Never change what the code does. If it isn't tested, write a characterization test that pins current behavior before refactoring.
2. Simpler, not cleverer. Aim for code a tired developer reads at a glance — not a showcase of conditional types. A clever line that needs a comment has failed, and a type that needs a comment has failed twice.