skills.rest
catowabisabi
catowabisabiCOMMUNITY
Explore all skills by this author →
GitHub

logic-bug-scan

Identify logical bugs, state inconsistencies, and race conditions in code.

Updated Aug 23, 2026
Search Tags:#static-analysis#error-handling#code-review#race-condition#logic-bug#unreachable-code
One-click install
npx skills add https://github.com/catowabisabi/Agentic-RAG-LLMs-API --skill logic-bug-scan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: logic-bug-scan
Source: https://github.com/catowabisabi/Agentic-RAG-LLMs-API/tree/main/.claude/skills/logic_bug_scanner_skill
Command: npx skills add https://github.com/catowabisabi/Agentic-RAG-LLMs-API --skill logic-bug-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strictly checks code logic errors, state anomalies, race conditions, and error handling.

Core Features & Use Cases

  • Thorough code review for logic bugs, state inconsistencies, race conditions, and missing error handling.
  • Detect unreachable or incorrectly assumed code paths and improve reliability.
  • Use cases include auditing modules, validating critical components, and preparing production-ready code.

Quick Start

Paste the code or repository path to scan and receive a structured bug report with potential bugs, causes, and severities.

Frequently Asked Questions about logic-bug-scan

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

FAQPage Schema
How do I detect race conditions and state inconsistencies during a code review?▼

Detect race conditions and state inconsistencies by applying deterministic scanning rules to your code, which identifies potential bugs across modules and concurrent workflows to produce a structured severity report.

How do I find unreachable code paths and missing error handling before production deployment?▼

Find unreachable code paths and missing error handling by scanning the repository to validate critical components, ensuring production-ready code reliability through structured bug and cause reporting.

What is the best way to audit concurrent workflows for logical bugs and state anomalies?▼

Auditing concurrent workflows for logical bugs involves strictly scanning code logic to identify state anomalies and race conditions, yielding a structured report with potential bugs, causes, and severities for remediation.

Can I scan an entire repository path for logical bugs and error handling issues?▼

You can scan an entire repository path by pasting it into the scanner, which applies deterministic rules across modules and services to output a structured report detailing potential bugs, causes, and severities.

Does static analysis for logic bugs work on critical components in production environments?▼

Static analysis for logic bugs works on critical components in production environments by applying deterministic scanning rules across modules and concurrent workflows to detect state anomalies and guide remediation.

Related Skills

Explore More Software Engineering Skills→
llmh333llmh333

repo-scan

Classify repository files into project code, embedded third-party, or build artifacts.

Community
Advanced
InNoobWeTrustInNoobWeTrust
4

edge-case-hunter

Enumerate branching paths to expose unguarded edge cases in code.

Community
Advanced
noundernounder
3

effect-testing

Test Effect.ts success and failure paths with deterministic concurrency handling.

Community
Intermediate
ricablericable
1

Pair Programming

Facilitate AI-assisted pair programming with dynamic role management and automated verification.

Community
Advanced