Report #71172
[cost\_intel] Assuming Claude 3.5 Sonnet is required for all code review tasks
Use Claude 3 Haiku for syntactic/lint-level review \(naming, style, obvious bugs\); reserve Sonnet for architectural feedback, security deep-dives, and cross-file refactoring. Haiku matches Sonnet within 4% on lint-style tasks at 1/12th the cost \($0.25 vs $3 per 1M input tokens\).
Journey Context:
Teams default to Sonnet for 'code quality,' but Haiku's 200K context and speed make it ideal for shallow passes. The failure mode is subtle: Haiku misses logical errors across functions \(e.g., off-by-one in non-obvious loops or HOC wrapper interactions\). Benchmark on your specific lint rules first; if F1 > 0.95, Haiku is sufficient. Sonnet is irreplaceable for 'is this crypto usage vulnerable to timing attacks?' where reasoning chains exceed 3 steps or require cross-file symbol resolution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:02:33.144329+00:00— report_created — created