codex-bug

Diagnose GitHub bug reports from openai/codex and recommend next actions.

5|1|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/looooonk/better-codex --skill codex-bug-looooonk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-bug
Source: https://github.com/looooonk/better-codex/tree/main/.codex/skills/codex-bug
Command: npx skills add https://github.com/looooonk/better-codex --skill codex-bug-looooonk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Triage of incoming bug reports for the openai/codex repository is time-consuming: maintainers must fetch issue details, assess reproducibility, and decide whether to investigate, request more information, or close the report as not a bug. This Skill automates that diagnostic workflow. ## Core Features & Use Cases - Issue Retrieval via GitHub API: Fetches the issue body and comments from api.github.com/repos/openai/codex as the source of truth, avoiding noisy HTML scraping. - Structured Triage Decision: Summarizes the report (repro steps, expected vs actual behavior, environment, logs) and decides between verifying against sources, requesting more information, or explaining why it is not a bug. - Use Case: A maintainer receives a link to a vague bug report about Codex CLI crashes. The Skill pulls the issue and comments, notes that logs and environment details are missing, and drafts a request for the specific information needed to reproduce the problem. ## Quick Start Analyze this GitHub issue from openai/codex and tell me whether to verify it, ask for more info, or explain why it is not a bug: https://github.com/openai/codex/issues/1234

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 evidence, then recommends verifying against sources, requesting more information, or explaining why it is not a bug.

How to fetch GitHub issue details without scraping HTML?▼

Use the GitHub REST API endpoints: /repos/openai/codex/issues/<number> for the issue and /issues/<number>/comments for discussion. The API returns structured JSON that is cleaner and more reliable than parsing the HTML issue page.

What happens if network access to GitHub is blocked?▼

The Skill always attempts network access first and requests approval if the environment requires it. Only after a failed attempt 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 documented behavior or current constraints, citing evidence from the issue itself and any local sources checked. The Skill requires concrete evidence rather than assumptions before reaching this conclusion.

What information should a reproducible bug report include?▼

A reproducible report needs clear repro steps, expected versus actual behavior, environment details, and logs or session output. If any of these are missing, the Skill recommends requesting the specific gaps from the reporter.