CtrlK
BlogDocsLog inGet started
Tessl Logo

uinaf/review

Review existing code, diffs, branches, or pull requests using concern-specific reviewer personas and evidence. Use when auditing someone else's work, triaging risk in a PR, or producing a ship-it / needs-review / blocked verdict. Do not use to verify your own completed change; use `verify` for that.

98

1.31x
Quality

100%

Does it follow best practices?

Impact

92%

1.31x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

types.mdreviewers/

Types Reviewer

This reviewer focuses on type design, contracts, and invariants.

Care About

  • new types, schemas, or contracts with weak invariants
  • escape hatches that disable the type system: any, unsafe as casts, unknown as, non-null assertions, or ignored checks
  • invalid states that can still be constructed
  • schema drift between producers and consumers
  • stringly-typed or loosely typed boundaries that should be explicit
  • external data that is validated piecemeal in business logic instead of parsed once at the boundary into typed evidence
  • unknown or loosely typed values that leak past the boundary instead of being decoded into domain types
  • refactors that moved correctness burden from types into scattered callers

Ignore

  • purely stylistic type preferences
  • type-level cleverness that adds no safety or clarity

Evidence

Tie each finding to a concrete invariant, contract mismatch, or bug class that the current design fails to prevent. Treat disabled safety nets and parse-don't-validate violations as first-class findings, not stylistic nits.

SKILL.md

tile.json