speckit-review-errors

Audit speckit error handling for silent failures and inadequate logging.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/payangar-dev/texlab --skill speckit-review-errors-payangar-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-review-errors
Source: https://github.com/payangar-dev/texlab/tree/main/.agents/skills/speckit-review-errors
Command: npx skills add https://github.com/payangar-dev/texlab --skill speckit-review-errors-payangar-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps prevent obscure, hard-to-debug issues by auditing error handling so failures are surfaced, logged, and actionable instead of silently ignored.

Core Features & Use Cases

  • Silent failure detection: Identifies error states where execution continues without clear logging or user feedback.
  • Catch/block specificity review: Flags overly broad exception handling that can hide unrelated defects.
  • Actionable error messaging: Ensures user-facing errors explain what went wrong and what to do next, with appropriate severity and context.

Quick Start

Ask the AI to review error handling in the speckit project by checking changed files for silent failures, broad catches, weak logging, and non-actionable error messages.

Frequently Asked Questions about speckit-review-errors

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

FAQPage Schema
How do I find silent failures and empty catch blocks in my codebase?

Silent failure detection audits catch blocks and error callbacks to identify execution paths continuing without clear logging or user feedback. This prevents obscure issues by ensuring failures are surfaced and actionable instead of ignored.

How do I review overly broad exception handling in pull requests?

Catch block specificity review flags overly broad exception handling in changed files that can hide unrelated defects. It enforces explicit fallback justification and strong propagation behavior to prevent masked errors.

What is the best way to audit error logging and debuggability?

Logging audit reviews exception handling constructs to ensure failures are logged with sufficient context and severity tags. It eliminates weak logging by enforcing actionable error reporting across the codebase.

How do I ensure user-facing error messages are actionable?

Actionable error messaging audits user-facing errors to verify they explain what went wrong and what to do next. It enforces severity-tagged reporting with sufficient context for robust messaging.

How do I check changed files for inadequate error handling and weak logging?

Changed-file review applies pull request checks to exception handling constructs, error callbacks, and fallbacks. It detects silent failures, broad catches, weak logging, and non-actionable error messages.