code-check-error-boundaries

What problem does it solve?

This Skill prevents user-facing blank screens, infinite spinners, silent corruption, and non-recoverable UI states by auditing common failure paths after new routes, mutations, and async flows are added.

Core Features & Use Cases

• Checks loader and route error coverage: Finds TanStack/Router route loaders that lack an errorComponent, which otherwise can fail silently.
• Verifies mutation failure UX: Ensures useMutation calls either define onError or rely on a global default so errors don’t vanish behind generic or missing UI feedback.
• Validates submit and async resilience: Flags form submit buttons that aren’t disabled during pending requests, and identifies fire-and-forget async promise rejections in background/webhook-style code paths.
• Reviews error messaging with recovery: Detects generic error toasts that provide no retry affordance, leaving users without a path forward.

Quick Start

Run code-check-error-boundaries to audit the failure paths introduced by your latest UI changes and produce a ranked list of missing error handling and user-recovery gaps.