skills.rest
ngx-signal-forms
ngx-signal-formsOFFICIAL
Explore all skills by this author →
GitHub

silent-failure-hunter

Analyze error handling and logging in pull request diffs to identify silent failures.

3|2|Updated Oct 9, 2025
Search Tags:#debugging#logging#audit#error-handling#pr-review#silent-failure
One-click install
npx skills add https://github.com/ngx-signal-forms/ngx-signal-forms --skill silent-failure-hunter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: silent-failure-hunter
Source: https://github.com/ngx-signal-forms/ngx-signal-forms/tree/main/.github/skills/pr-toolkit/silent-failure-hunter
Command: npx skills add https://github.com/ngx-signal-forms/ngx-signal-forms --skill silent-failure-hunter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps reviewers proactively audit error handling in code changes, ensuring that every failure surfaces, is logged, and provides clear user feedback rather than being quietly swallowed.

Core Features & Use Cases

  • Identify try-catch and error-handling blocks and assess their specificity and logging quality.
  • Verify that user-facing messages are actionable and that failures propagate to appropriate handlers or dashboards.
  • Recommend explicit fallbacks and meaningful error codes to aid future debugging and monitoring.

Quick Start

Run the silent-failure-hunter agent on the latest PR diff to surface silent failures and ensure review-ready error handling.

Frequently Asked Questions about silent-failure-hunter

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

FAQPage Schema
How do I audit error handling for silent failures in a pull request?▼

To audit error handling for silent failures in a pull request, analyze the PR diff to identify try-catch blocks and assess their specificity, logging quality, and user feedback to surface hidden issues.

What is a silent failure in code and how does error handling mitigate it?▼

A silent failure occurs when an error is quietly swallowed without logging or user feedback. Error handling mitigates this by enforcing explicit fallbacks, actionable messages, and traceable error reporting to ensure every failure surfaces appropriately.

How do I ensure user-facing error messages are actionable during code review?▼

To ensure user-facing error messages are actionable during code review, verify that failures propagate to appropriate handlers and recommend explicit fallbacks alongside meaningful error codes to aid future debugging and monitoring.

Does this silent failure detection work on PR diffs without external dependencies?▼

Yes, silent failure detection works directly on PR diffs without external dependencies. It analyzes the latest code changes to surface hidden issues and enforces review-ready error handling natively.

What is the best way to enforce explicit fallbacks and traceable error reporting?▼

The best way to enforce explicit fallbacks and traceable error reporting is to audit PR error handling by verifying that user-facing messages are actionable and that failures propagate to appropriate handlers or dashboards.

Related Skills

Explore More Software Engineering Skills→
nillenille

Code Review

Review code diffs for correctness, security, and conventions.

Community
Advanced
TechyMTTechyMT
5

error-handling

Convert tool errors into readable LLM feedback with typed propagation.

Community
Intermediate
benshapyrobenshapyro
9

error-handler

Standardize exception management with custom error classes and structured logging for TypeScript and Python.

Community
Intermediate
hatlesswizardhatlesswizard
4

clean-code-ch07-error-handling

Audit exception usage and error-handling structure across Java, Python, and C# codebases.

Community
Advanced