speckit-review-errors

Audit error handling code paths for silent failures and inadequate logging.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-review-errors-pradeepmouli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-review-errors
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-review-errors
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-review-errors-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Error handling review to uncover silent failures, weak logging, and untestable error paths that degrade reliability.

Core Features & Use Cases

  • Identify all try-catch blocks and error propagation patterns across a codebase.
  • Evaluate logging quality, error identifiers, and user-facing messages for clarity.
  • Provide actionable recommendations and guardrails to improve resilience during code reviews and PRs.

Quick Start

Run a structured error-handling audit on the target project and produce a prioritized list of fixes.

Frequently Asked Questions about speckit-review-errors

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

FAQPage Schema
How do I audit error handling to find silent failures in my codebase?

Auditing error handling identifies all try-catch blocks and fallback logic to surface silent failures and inadequate logging. It evaluates error propagation paths to ensure exceptions are narrowly scoped and properly categorized for reliability.

What is the best way to improve logging quality during code reviews?

Improving logging quality during code reviews involves evaluating existing logs for actionability and traceable identifiers. The audit checks user-facing messages and error identifiers to ensure failures are clearly surfaced and testable.

How do I check if my pull requests have inadequate error propagation?

Checking pull requests for inadequate error propagation involves applying a structured audit to changed files. It targets try-catch blocks and fallback logic to ensure exceptions are narrowly scoped and failures are not silently ignored.

Can I run an error handling audit on an entire repository or just PRs?

You can run an error handling audit on an entire repository, specific changes, or pull requests. The audit focuses on try-catch blocks, error propagation, and user-facing messages to produce a prioritized list of resilience fixes.

Why are silent failures in try-catch blocks degrading my application reliability?

Silent failures in try-catch blocks degrade reliability because exceptions are caught without proper logging or propagation. This audit surfaces those weak error paths, ensuring errors have traceable identifiers and actionable logs for debugging.