reliability-scan

Analyzes error handling, failure isolation, recovery, and crash safety in a codebase.

3|1|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/zeljkoobrenovic/sokrates-skills --skill reliability-scan-zeljkoobrenovic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reliability-scan
Source: https://github.com/zeljkoobrenovic/sokrates-skills/tree/main/skills/scanners/reliability-scan
Command: npx skills add https://github.com/zeljkoobrenovic/sokrates-skills --skill reliability-scan-zeljkoobrenovic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Codebases encode implicit theories of failure that are hard to audit manually: swallowed exceptions, missing timeouts, non-atomic writes, and unbounded retries hide in thousands of call sites. This Skill reads the error-handling code of a project and produces a verifiable reliability report describing how the system behaves when dependencies, the network, the disk, or its own logic fail. ## Core Features & Use Cases - Error model and handling analysis: Maps exception/Result conventions, central error types, swallowed or catch-all handlers, panics on runtime input, and success-reported-after-failure patterns. - Isolation, recovery, and degradation review: Traces process/task/plugin boundaries, retries, timeouts, circuit breakers, fallbacks, and offline modes, citing the exact constants and code. - Crash safety and shutdown audit: Checks atomic writes, fsync, cleanup on failure paths, signal handling, and shutdown order, then synthesizes a reliability posture with blast-radius assessment. - Use Case: Point it at a repository with a Sokrates _sokrates analysis to receive a validated reliability-scan.json findings report plus an interactive HTML explorer, with severity-calibrated findings and stable IDs that diff across runs. ## Quick Start Ask the AI to run the reliability scan on this repository and report how the system behaves when its main dependencies fail.

Frequently Asked Questions about reliability-scan

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

FAQPage Schema
How do I audit error handling in a codebase?

Run the reliability scan, which counts handling sites with a deterministic script, then reads the load-bearing files: the main loop, persistence writers, external-call wrappers, and shutdown path. It produces findings on swallowed errors, catch-all handlers, retries, timeouts, and crash safety with cited evidence.

What does a reliability review of code cover?

It covers the error model (exception vs Result types), call-site handling, failure isolation across process and task boundaries, recovery mechanisms like retries and circuit breakers, designed degradation, and resource safety including atomic writes and orderly shutdown.

Does the reliability scan require a Sokrates analysis?

No, it works best with a Sokrates _sokrates folder for component names and hotspots but degrades gracefully without one. Prior scanner findings like tech-stack and architecture help orient the analysis but are optional.

Which programming languages does the counting script support?

The count_handling_sites.py script supports Rust, Java, Kotlin, Scala, JavaScript, TypeScript, Python, Go, and C#. It excludes test code by path conventions and, for Rust, skips #[cfg(test)] modules.

How are reliability findings deduplicated across runs?

Findings use stable IDs built from fixed slugs per group, such as recovery/outgoing-retry or resources/persisted-state, naming mechanisms rather than consequences. This lets two runs on an unchanged tree produce matching IDs that diff cleanly.