reviewing-silent-failures

Detect silent failures in JavaScript/TypeScript frontend code.

11|1|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/thkt/claude-config --skill reviewing-silent-failures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-silent-failures
Source: https://github.com/thkt/claude-config/tree/main/skills/reviewing-silent-failures
Command: npx skills add https://github.com/thkt/claude-config --skill reviewing-silent-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams detect and address silent failures in frontend code, ensuring errors are visible, debuggable, and communicated to users.

Core Features & Use Cases

  • Detection: Identify empty catch blocks, unhandled promises, console-only errors, and missing error boundaries.
  • Guided References: Provides references for error handling patterns and best practices.
  • Usage Scenarios: Quickly audit a React app for robust error handling and resilient UI.

Quick Start

Give Claude a project to audit, for example: "Review silent failures in my React app and surface potential issues." Or "Run a silent-failure audit against the frontend codebase."

Frequently Asked Questions about reviewing-silent-failures

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect silent failures in my React application?

Silent failures occur when errors are caught but not logged or handled visibly. Detect them by auditing for empty catch blocks, unhandled promise rejections, console-only errors, and missing error boundaries in your React codebase. This Skill surfaces these patterns with contextual logging and actionable remediation guidance.

What are empty catch blocks and why are they a problem in TypeScript frontend code?

Empty catch blocks silently swallow errors without logging or recovery. In TypeScript and JavaScript frontends, they prevent debugging and hide failures from users. This Skill identifies empty catch patterns and recommends error boundaries and logging strategies to make failures visible.

How do I handle unhandled promise rejections in modern JavaScript?

Unhandled promise rejections occur when .catch() is omitted or errors aren't propagated. This Skill detects fire-and-forget patterns and surfaces best practices for promise error handling, ensuring failures reach error boundaries or logging systems instead of failing silently.

Can I use this to audit error handling across an entire frontend codebase?

Yes. Provide your React or TypeScript project to audit for silent failures across all files. The Skill identifies patterns like console-only errors, missing error boundaries, and unhandled promises, then delivers references and remediation paths for robust, debuggable error handling.

What's the difference between error boundaries and try-catch blocks in React?

Error boundaries catch component render failures; try-catch blocks catch synchronous errors in event handlers and async code. This Skill guides you on placement and context for each, ensuring both are used appropriately to surface failures instead of crashing silently.