code-logic-checker

Detect logic bugs, contradictions, and missing edge cases in code and requirements.

1|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/JimmyTranDev/dotfiles --skill code-logic-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-logic-checker
Source: https://github.com/JimmyTranDev/dotfiles/tree/main/src/opencode/skills/code-logic-checker
Command: npx skills add https://github.com/JimmyTranDev/dotfiles --skill code-logic-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that logic is sound. Find contradictions, invalid assumptions, flawed reasoning, and logical gaps in code and requirements.

Core Features & Use Cases

  • Internal checks: Detect dead code and unreachable branches, missing return paths, and unsafe assumptions.
  • Policy & requirements analysis: Analyze requirements for contradictions, implicit dependencies, and inconsistent constraints.
  • Risk evaluation: Provide structured guidance on potential logic failures and recommended fixes.

Quick Start

Ask the analyzer to identify contradictions, invalid assumptions, and missing edge cases in the provided code or requirements and suggest concrete fixes.

Frequently Asked Questions about code-logic-checker

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

FAQPage Schema
How do I find logic bugs and missing edge cases in my code?

Static analysis detects logic bugs by finding dead code paths, incomplete state transitions, and unsafe assumptions across your codebase. It applies reasoning checks to identify dead branches, contradictory conditions, and missing return paths, then suggests concrete fixes.

What is the best way to check requirements documents for contradictions?

Analyzing requirements for contradictions involves checking design specs for inconsistent constraints and implicit dependencies. This identifies invalid assumptions and logical gaps in requirements documents before implementation begins.

Can I use static analysis to detect dead code paths and unsafe null handling?

Yes, static analysis detects dead code paths and unsafe null handling by applying static reasoning checks. It identifies unreachable branches and contradictory conditions across various programming languages without executing the code.

Does logic analysis work on design specs and requirements across different languages?

Logic analysis works on design specs and requirements across different programming languages and development stages. It evaluates incomplete state transitions and unsafe assumptions to verify logic in both code and documentation.

How do I fix unreachable branches and incomplete return paths identified during code analysis?

Fixing unreachable branches and incomplete return paths requires applying structured guidance generated after code analysis. This guidance provides concrete fixes for detected dead code, flawed reasoning, and unsafe assumptions.

When should I analyze my codebase for missing state transitions and invalid assumptions?

Analyze codebases for missing state transitions and invalid assumptions whenever verifying sound logic across development stages. This detects flawed reasoning and logical gaps in requirements to prevent potential logic failures.