Skip to content
Skills Library
Programming · Analysis

exception-flow-analysis

/exception-flow-analysis

Traces how errors and exceptions flow through critical code paths to find swallowed errors and broken propagation. Use when analyzing exception handling on important paths.

Licence
CC0-1.0
Last repository change
03.06.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 03.06.2026, without references to retired models or APIs.

Licence

CC0-1.0, otwarta.

What it does and when to use it

Traces how errors and exceptions flow through critical code paths to find swallowed errors and broken propagation. Use when analyzing exception handling on important paths.

Arguments

/exception-flow-analysis [path or scope]
Original author description

Traces how errors and exceptions flow through critical code paths to find swallowed errors and broken propagation. Use when analyzing exception handling on important paths.

How it works

  1. Provide:
  2. Constraints & style:
Original SKILL.md headings · 56 lines, 225 words
SKILL.md preview
---
name: exception-flow-analysis
description: Traces how errors and exceptions flow through critical code paths to find swallowed errors and broken propagation. Use when analyzing exception handling on important paths.
license: CC0-1.0
metadata:
  category: code-quality
allowed-tools: Read Grep Glob Write
disable-model-invocation: true
argument-hint: "[path or scope]"
---

**Target:** $ARGUMENTS

If no target path is given above, review the entire codebase.

---

Trace error flow through the application:

Critical paths to analyze:
1. Database connection failure
2. Third-party API timeout
3. Invalid user input
4. Authentication failure
5. File system errors

For each path, verify:
- Where is the error caught?
- How is it transformed?
- What gets logged?
- What does the user see?
- Is the system state consistent?

In the audit report, document the error flow as a text diagram or structured list showing:
- Error origin points
- Transformation layers
- Final handling points
- Recovery mechanisms

Anti-patterns to identify:
- Swallowed exceptions (empty catch blocks)
- Generic catch-all handlers hiding specific errors
- Errors used for flow control
- Missing error boundaries
- Inconsistent error formats

Provide a standardized error handling template.

## Provide:

A structured finding report

A scale of 1/10 on how important each finding is

Remediation: precise code-level fix or config change (snippets welcome) if possible

## Constraints & style:

Be concrete and cite exact code locations and identifiers.

Prefer minimal, drop-in fix snippets over prose.

Do not invent files or functions that aren’t present; if context is missing, mark as Unable to verify and say what code would prove it.

Write this into a markdown file and place it in the audits/ folder.

Versions

The database has no other skills named exception-flow-analysis.

Database snapshot: 13.11.2026 · package version 3a814b4b2fc9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100error-handling-review
    Audits how code detects, propagates, retries, times out, logs, and surfaces errors - swallowed exceptions, missing timeouts, unsafe retries, lost context, leaky user-facing messages, and partial-failure cleanup. Use when reviewing a service, integration, or pull request for…
  • 100143-java-functional-exception-handling
    Use when you need to apply functional exception handling best practices in Java — including replacing exception overuse with Optional and VAVR Either types, designing error type hierarchies using sealed classes and enums, implementing monadic error composition pipelines,…
  • 100php-error-handling
    Implement modern PHP error and exception handling patterns. Use when implementing exception hierarchies, error handlers, or custom exceptions in PHP.
  • 100langchain-common-errors
    Diagnose and fix common LangChain errors and exceptions. Use when encountering LangChain errors, debugging failures, or troubleshooting integration issues. Trigger with phrases like "langchain error", "langchain exception", "debug langchain", "langchain not working", "langchain troubleshoot".
  • 100flow-map
    Use when the user wants every path through a feature mapped before coding: happy paths, validation and auth failures, network errors, concurrency conflicts, timeouts, and recovery, or asks what are all the paths or for a state diagram.
  • 85backend-error-observability-review
    Use when reviewing code for error handling, exception flow, logging, metrics, and tracing concerns. Triggers when exception handlers, error responses, logging calls, or observability instrumentation are in scope.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.