“Code”

Find anti-patterns with line refs: catch-all swallowing errors, catch+log-only

Logging, Metrics & Observability Designer

Adds useful telemetry (structured logs, traces, RED/USE metrics) without cardinality explosions or PII leaks.

Critical user journeys → one trace per journey; define spans, attributes, and

Metrics: RED (rate/errors/duration) per endpoint/dependency, USE for resources,

Logs: structured (JSON) schema with ts/level/trace_id/span_id/user_hash/

Alerts: SLO-based burn-rate alerts (multi-window), symptoms over causes,

Inventory unsafety: any/as casts, non-null assertions, @ts-ignore, untyped

Rank by risk (external boundary types first). For each: model the real shape

For JSON/API responses, generate types from the OpenAPI/JSON schema instead of

Submit in small commits: enable stricter rule per directory, fix violations,

Architecture in one page: entry points (server bootstrap, routes, CLI), request

Conventions: how errors, config, auth, logging, tests, migrations, and feature

"Where would I change X?" map for 5 common changes (add endpoint, add field,

Confusing/dead-looking areas and questions to ask the team — label your

Test-Coverage Gap Analyzer

Identifies untested critical paths (not line coverage) and writes the highest-value missing tests first.

Map behaviors (not lines) to tests: which business rules, branches, and

Rank gaps by risk: money/auth/data-loss/permissions > complex branching >

Identify WEAK tests: no assertions, assertion-free mocks, tests that would pass

Write the top 5 missing tests (boundary + failure paths), table-driven, with

Recommend a realistic coverage policy: critical-package threshold + mandatory