risk-scan

Scan repository code for failure modes and rank findings by severity.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dimakis/mitzo --skill risk-scan-dimakis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk-scan
Source: https://github.com/dimakis/mitzo/tree/main/skills/risk-scan
Command: npx skills add https://github.com/dimakis/mitzo --skill risk-scan-dimakis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you detect hidden software risks early by scanning the specified code area for missing error handling, edge-case gaps, weak test coverage, unsafe assumptions, and security issues.

Core Features & Use Cases

  • Risk-focused review: Identifies failure scenarios such as unhandled promise rejections, missing null checks, and uncaught exceptions.
  • Edge-case coverage gaps: Surfaces problems around empty inputs, boundary values, concurrency, and race conditions.
  • Security and safety checks: Highlights injection vectors, path traversal, unvalidated inputs, and potential secret exposure.
  • Test completeness: Flags critical paths that lack tests, including untested error branches.

Quick Start

Run risk-scan against the relevant directory (for example, a backend route folder) to get a ranked list of failure modes with severity and mitigation suggestions.

Frequently Asked Questions about risk-scan

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

FAQPage Schema
How do I find missing error handling and edge cases in my codebase?

To find missing error handling and edge cases, scan the specified repository area to detect unhandled promise rejections, missing null checks, uncaught exceptions, and boundary value gaps, producing a ranked list of failure modes by severity.

What is static analysis for security risks and unsafe assumptions?

Static analysis for security risks identifies injection vectors, path traversal vulnerabilities, unvalidated inputs, and potential secret exposure by scanning source code without executing it, highlighting unsafe assumptions in critical modules.

How do I check test coverage for untested error branches?

Check test coverage for untested error branches by scanning critical code paths to flag missing tests, ensuring that both standard execution routes and failure scenarios receive adequate test completeness validation.

Does risk-focused code review work for specific directories or file sets?

Yes, risk-focused code review works for specific directories or file sets by accepting directory paths as arguments, enabling targeted analysis of critical modules where robustness, correctness, and security are uncertain.

Can static analysis modify my source files during a risk assessment?

No, static analysis during risk assessment enforces read-only analysis without making file changes, ensuring the specified repository area remains unmodified while producing ranked findings and mitigation guidance.