What problem does it solve? Codebases often swallow errors silently, throw untyped values, miss error boundaries, or lack production observability, and these structural gaps are hard to spot in manual review. This Skill statically audits a TypeScript codebase against an opinionated four-layer error-handling baseline and reports concrete violations with file and line references. ## Core Features & Use Cases - Four-layer audit: Covers throw and catch hygiene, async and network error handling, React error boundaries, and logging and observability, preceded by a diagnostic snapshot of try/catch counts, async style, and detected tooling. - Structured findings contract: Writes findings.md, findings.json (schema 2.0.0), snapshot.md, and metadata.json to .architect-audits/error-handling-audit/ for scoring and roll-up into a Repository Quality Score. - Optional implementation plan: After reporting, asks whether to generate a descriptive Markdown plan detailing which catch blocks, call sites, boundaries, and observability primitives to fix. - Use Case: Run /error-handling-audit on a Next.js app before a release to surface empty catch blocks, fetch calls without timeouts, missing route-level error boundaries, and an unconfigured Sentry sample rate, then generate a remediation plan. ## Quick Start Run /error-handling-audit in the root of a TypeScript project to produce a findings report and optionally generate an implementation plan for the gaps.
