reliability-reviewer

To identify missing timeouts and error handling in code reviews, analyze I/O boundaries like HTTP calls and DB queries for explicit checks against unsafe retry loops, missing backoffs, and dangerous fallback logic that can cascade failures.

The best way to prevent cascading failures across service boundaries is to assess production reliability gaps by enforcing explicit checks for fault tolerance, safe error propagation, and avoiding dangerous fallback logic during code reviews.

You review code for unsafe retry loops and missing backoff strategies by scanning service boundaries and I/O flows for explicit fault-tolerance mechanisms, ensuring dangerous retry configurations are remediated with concrete recovery guardrails.

Yes, you can use a reliability-focused review to detect fault tolerance gaps in background jobs by assessing I/O boundaries for missing error propagation, unsafe fallback logic, and lack of proper recovery guidance.

Missing error propagation on database queries causes production outages because unhandled exceptions on I/O boundaries can trigger cascading failures, bypassing resilience guardrails like timeouts and backoffs needed for system stability.