codex-bug

Diagnose GitHub bug reports in openai/codex and decide verification or follow-up actions.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/sjc786526-coder/RONDO --skill codex-bug-sjc786526-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-bug
Source: https://github.com/sjc786526-coder/RONDO/tree/main/multidev/.codex/skills/codex-bug
Command: npx skills add https://github.com/sjc786526-coder/RONDO --skill codex-bug-sjc786526-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Triage of incoming bug reports for the openai/codex repository is time-consuming: maintainers must fetch the issue, extract repro details, and decide whether to verify against source code, request more information, or explain why the behavior is not a bug. This Skill standardizes that diagnostic workflow. ## Core Features & Use Cases - GitHub API-Based Issue Retrieval: Fetches the issue and its comments via the GitHub API rather than scraping noisy HTML pages, using them as the source of truth. - Structured Bug Summary: Extracts title, body, repro steps, expected vs actual behavior, environment, logs, and thread IDs before any deep investigation. - Decision Workflow: Classifies each report into one of three outcomes—verify against Codex sources, request more information, or explain why it is not a bug with cited evidence. - Use Case: A maintainer pastes a link to an openai/codex issue and asks for triage; the Skill fetches the issue, summarizes the report, inspects relevant code, and recommends the next action. ## Quick Start Diagnose the bug reported at this openai/codex GitHub issue URL and tell me whether to verify it, request more info, or close it as not a bug.

Frequently Asked Questions about codex-bug

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

FAQPage Schema
How do I triage a GitHub bug report for openai/codex?▼

Provide the issue URL from github.com/openai/codex/issues. The Skill fetches the issue and comments via the GitHub API, summarizes the reported behavior and repro steps, then recommends verifying against sources, requesting more info, or closing as not a bug.

How to fetch GitHub issue details without scraping HTML?▼

Use the GitHub API endpoints api.github.com/repos/openai/codex/issues/<number> for the issue and /comments for discussion. The API responses are cleaner than HTML pages and serve as the source of truth for the report.

What happens if network access to GitHub is unavailable?▼

The Skill always attempts network access first and requests approval if the environment requires it. Only after the attempt fails does it fall back to offline options, such as drafting a response template, and asks how to proceed.

When should a bug report be closed as not a bug?▼

Close as not a bug when the report contradicts current documented behavior or constraints. The decision must cite evidence from the issue itself and any local Codex sources inspected, rather than relying on assumption.

What information makes a bug report ready for verification?▼

A report is ready to verify when it includes specific repro steps, expected versus actual behavior, environment details, and logs or session details. Vague reports missing these elements should receive a request for more information instead.