bugs

Identify code bugs via static analysis and report structured JSON with severity and remediation.

145|21|Updated Jan 2, 2026

Search Tags:#debugging #codex #static-analysis #bug-hunting #json-output #multifile #race-conditions

Ready to run

npx skills add https://github.com/alfredolopez80/multi-agent-ralph-loop --skill bugs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bugs
Source: https://github.com/alfredolopez80/multi-agent-ralph-loop/tree/main/.claude/skills/bugs
Command: npx skills add https://github.com/alfredolopez80/multi-agent-ralph-loop --skill bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug hunting with Codex CLI automates deep static analysis to uncover logic errors, race conditions, and other defects across codebases, saving time and improving release quality.

Core Features & Use Cases

Static analysis with TLDR-context for efficient code understanding.
Multi-file analysis across modules to correlate bugs across boundaries.
Severity-based JSON output with details like file, line, type, and remediation steps.
Integration with Ralph Loop workflows and debugging pipelines for iterative fixes.
CLI-based bug hunting on directories or entire codebases.

Quick Start

Run ralph bugs on a target directory to initiate a Codex-based bug-hunting session.

Frequently Asked Questions about bugs

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

FAQPage Schema

How do I find race conditions and logic errors across multiple files in a codebase?▼

Static analysis bug hunting traces race conditions and logic errors across multi-file modules to pinpoint defects. It scans directories or repositories to correlate bugs across module boundaries and delivers structured JSON output with severity, file, and line details.

What is TLDR context in static analysis for bug hunting?▼

TLDR context is a code understanding mechanism used in static analysis bug hunting to efficiently summarize repository logic. It enables deep Codex-powered bug hunting by providing concise context when tracing bugs across large codebases.

Can I run static analysis on an entire repository to find bugs?▼

Yes, repository-level static analysis is supported. Bug hunting executes on single files, specific directories, or entire codebases to trace bugs across modules and generate structured JSON reports with remediation steps.

Does the bug hunting output include remediation steps and severity levels?▼

Yes, bug hunting output includes remediation steps and severity levels. The analysis delivers structured JSON containing bug type, affected file, line number, severity rating, and specific remediation guidance for each defect.

What is the best way to integrate static analysis into a debugging pipeline?▼

Static analysis integrates into debugging pipelines through Ralph Loop workflows and ad hoc review hooks. This enables iterative bug hunting where identified defects feed back for verification and fixes are optionally tested for reproduction.

Do I need to write tests to verify the bugs found during static analysis?▼

Tests are optional but supported for verifying bug fixes. The bug hunting workflow can include optional tests to reproduce identified defects and verify applied remediations effectively resolve the logic errors or race conditions.