skills.rest
lexicalninja
lexicalninjaCOMMUNITY
Explore all skills by this author →
GitHub

bug-detector

Detect bugs, logic errors, and edge cases across codebases with structured reports.

2|Updated Jan 15, 2026
Search Tags:#edge-cases#bugs#static-analysis#error-handling#code-review#bug-report#detect
One-click install
npx skills add https://github.com/lexicalninja/my-little-scrum-team --skill bug-detector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-detector
Source: https://github.com/lexicalninja/my-little-scrum-team/tree/main/skills/bug-detector
Command: npx skills add https://github.com/lexicalninja/my-little-scrum-team --skill bug-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects bugs, logic errors, and edge cases in code for robust maintenance and quality assurance.

Core Features & Use Cases

  • Structured bug reports with file paths and line numbers
  • Checks for null/undefined, type errors, off-by-one, race conditions
  • Provides suggested fixes with rationale and priority

Quick Start

Provide your codebase or files to the bug-detector, and it will return structured bug reports with file paths, line numbers, descriptions, current code, suggested fixes, and priorities.

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 in my codebase?▼

To detect logic errors and edge cases, provide your source files or snippets to the bug-detector. It analyzes the code and returns structured bug reports with file paths, line numbers, descriptions, suggested fixes, and priority levels.

Can I check for race conditions and off-by-one errors in source code snippets?▼

Yes, you can check for race conditions and off-by-one errors by supplying explicit source snippets. The tool validates the input and reports these specific defects alongside null/undefined and type errors.

What is the best way to get structured bug reports with file paths and line numbers?▼

The best way to get structured bug reports with file paths and line numbers is to pass relevant codebase files for analysis. The output includes descriptions, current code, suggested fixes, rationale, and priority for each detected bug.

Does this bug detector work with multiple programming languages and project types?▼

Yes, this bug detector covers multiple languages and project types. It requires explicit inputs with the relevant source files or snippets to generate structured bug reports for the provided code.

Why do I need to provide explicit source files for static code analysis?▼

You need to provide explicit source files because the static analysis requires the actual codebase or snippets to validate null/undefined, type errors, off-by-one errors, and race conditions to generate accurate suggested fixes.

What suggested fixes are provided for null and undefined type errors?▼

For null and undefined type errors, the bug report provides suggested fixes with rationale and priority. It includes the current code, file paths, and line numbers to help you resolve the defects.

Related Skills

Explore More Software Engineering Skills→
hilaryosbornehilaryosborne

qa-problem-solving

Analyze bug reports to triage defects and plan resolutions.

Community
Intermediate
jpoleyjpoley
50

patch-engineer

Validate security patch quality and regression risk for code changes.

Community
Advanced
asgarovfasgarovf
23

debugging

Diagnose software bugs by analyzing stack traces and error messages.

Community
Intermediate
allanninalallanninal
1

semgrep

Scan codebases for security vulnerabilities and coding standards with Semgrep.

Community
Intermediate