check-errors

Scan codebases for swallowed exceptions, missing handlers, and reactive-chain issues.

4|Updated May 26, 2025
One-click install
npx skills add https://github.com/pwittchen/varun.surf --skill check-errors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-errors
Source: https://github.com/pwittchen/varun.surf/tree/main/.claude/skills/check-errors
Command: npx skills add https://github.com/pwittchen/varun.surf --skill check-errors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify error-handling gaps across codebases, including swallowed exceptions, missing handlers, inconsistent error responses, and gaps in reactive error handling.

Core Features & Use Cases

  • Detect swallowed exceptions in try/catch blocks and ensure proper handling and logging.
  • Validate reactive error handling in Mono/Flux chains and ensure onErrorResume/onErrorReturn usage where appropriate.
  • Analyze exception propagation, error response consistency, and coverage of global exception handling.
  • Identify resource cleanup issues on error paths and verify thorough logging for diagnostics.

Quick Start

Scan the repository to surface all error-handling gaps and generate actionable remediation steps.

Frequently Asked Questions about check-errors

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

FAQPage Schema
How do I find swallowed exceptions in a Spring Boot codebase?

To find swallowed exceptions in a Spring Boot codebase, scan controllers and services for try/catch blocks missing proper handling or logging, surfacing gaps as structured findings for remediation.

What is the best way to detect missing reactive error handling in Mono and Flux chains?

Detecting missing reactive error handling involves analyzing Mono and Flux chains to ensure onErrorResume and onErrorReturn patterns are used appropriately, preventing propagation issues and resource leaks.

How do I validate consistent error responses across Spring Boot controllers?

Validate consistent error responses across Spring Boot controllers by assessing exception propagation and verifying global exception handling coverage to enforce consistent error payloads throughout the project.

Why does my application lack context when logging exceptions in reactive streams?

Your application lacks logging context because exceptions are not properly wrapped with contextual information, causing diagnostic gaps when errors propagate through reactive streams and services.

Can I identify resource cleanup issues on error paths in a reactive application?

Yes, you can identify resource cleanup issues on error paths by scanning the reactive application's configuration and services to surface leaks and ensure exceptions are wrapped with appropriate context.