bug-detector

Analyze code to identify bugs, logic errors, and edge-case issues.

11|Updated Sep 5, 2025

Search Tags:#debugging #reporting #edge-cases #code-review #analyze #bug-detection #null-check

Ready to run

npx skills add https://github.com/thrawn01/claude-dotfiles --skill bug-detector-thrawn01

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-detector
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/bug-detector
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill bug-detector-thrawn01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects bugs, logic errors, and edge-case handling issues during code reviews. It helps identify runtime errors, null/undefined handling gaps, type mismatches, and unhandled edge cases, and returns structured bug reports with file paths, line numbers, current code, and suggested fixes.

Core Features & Use Cases

Detect null/undefined handling issues and type errors during code reviews
Identify off-by-one errors, logic errors, and potential race conditions
Produce structured bug reports including file path, line numbers, current code, suggested fix, reason, and priority

Quick Start

Feed the target codebase or a specific file to the detector and review the resulting structured bug reports

Frequently Asked Questions about bug-detector

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

FAQPage Schema

How do I detect logic errors and edge cases during a code review?▼

You can detect null and undefined handling issues by analyzing your codebase to identify runtime checks, type mismatches, and unhandled edge cases. The analysis returns structured bug reports with file paths, line numbers, and suggested fixes to resolve the null handling gaps.

How do I generate structured bug reports with file paths and suggested fixes?▼

Generate structured bug reports by feeding the target codebase or specific file to a detector that analyzes for bugs and logic errors. The resulting report includes the file path, line numbers, current code, suggested fix, reason, and priority for each identified issue.

Can I identify race conditions and off-by-one errors across different programming languages?▼

Yes, you can identify race conditions and off-by-one errors across different programming languages. The detection mechanism applies to code reviews across languages and projects, analyzing logic errors and edge-case handling scenarios regardless of the specific language used.

What is the best way to check for type validation and unhandled edge cases in a codebase?▼

The best way to check for type validation and unhandled edge cases is to analyze the code for type mismatches and runtime errors. This process identifies gaps in edge-case handling and outputs a prioritized report detailing current code and proposed fixes.

Do I need a specific framework to analyze potential race conditions in my code?▼

No, you do not need a specific framework to analyze potential race conditions. The detection process works across languages and projects without dependencies, identifying race-condition scenarios and returning structured reports with proposed fixes and priority levels.