Codex Bug
- 252 installs
- 104k repo stars
- Updated August 4, 2026
- openai/codex
Diagnose GitHub bug reports in openai/codex.
About
Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions. Diagnose a Codex GitHub bug report and decide the next action: verify against sources, request more info, or explain why it is not a bug.
- Diagnose a Codex GitHub bug report and decide the next action: verify against sources, request more info, or explain why
- Require a GitHub issue URL that points to `github.com/openai/codex/issues/…`.
- If the URL is missing or not in the right repo, ask the user for the correct link.
- Always access the issue over the network immediately, even if you think access is blocked or unavailable.
- Prefer the GitHub API over HTML pages because the HTML is noisy:
Codex Bug by the numbers
- 252 all-time installs (skills.sh)
- +14 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #2,510 of 16,556 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
codex-bug capabilities & compatibility
- Capabilities
- diagnose a codex github bug report and decide th · require a github issue url that points to `githu · if the url is missing or not in the right repo, · always access the issue over the network immedia
- Use cases
- documentation
What codex-bug says it does
Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining
npx skills add https://github.com/openai/codex --skill codex-bugAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 252 |
|---|---|
| repo stars | ★ 104k |
| Last updated | August 4, 2026 |
| Repository | openai/codex ↗ |
How do I apply codex-bug using the workflow in its SKILL.md?
Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, o...
Who is it for?
Developers following the codex-bug skill for the tasks it documents.
Skip if: Tasks outside the codex-bug scope described in SKILL.md.
When should I use this skill?
User mentions codex-bug or related triggers from the skill description.
What you get
Working codex-bug setup aligned with the documented patterns and constraints.
Files
Codex Bug
Overview
Diagnose a Codex GitHub bug report and decide the next action: verify against sources, request more info, or explain why it is not a bug.
Workflow
1. Confirm the input
- Require a GitHub issue URL that points to
github.com/openai/codex/issues/…. - If the URL is missing or not in the right repo, ask the user for the correct link.
2. Network access
- Always access the issue over the network immediately, even if you think access is blocked or unavailable.
- Prefer the GitHub API over HTML pages because the HTML is noisy:
- Issue:
https://api.github.com/repos/openai/codex/issues/<number> - Comments:
https://api.github.com/repos/openai/codex/issues/<number>/comments - If the environment requires explicit approval, request it on demand via the tool and continue without additional user prompting.
- Only if the network attempt fails after requesting approval, explain what you can do offline (e.g., draft a response template) and ask how to proceed.
3. Read the issue
- Use the GitHub API responses (issue + comments) as the source of truth rather than scraping the HTML issue page.
- Extract: title, body, repro steps, expected vs actual, environment, logs, and any attachments.
- Note whether the report already includes logs or session details.
- If the report includes a thread ID, mention it in the summary and use it to look up the logs and session details if you have access to them.
4. Summarize the bug before investigating
- Before inspecting code, docs, or logs in depth, write a short summary of the report in your own words.
- Include the reported behavior, expected behavior, repro steps, environment, and what evidence is already attached or missing.
5. Decide the course of action
- Verify with sources when the report is specific and likely reproducible. Inspect relevant Codex files (or mention the files to inspect if access is unavailable).
- Request more information when the report is vague, missing repro steps, or lacks logs/environment.
- Explain not a bug when the report contradicts current behavior or documented constraints (cite the evidence from the issue and any local sources you checked).
6. Respond
- Provide a concise report of your findings and next steps.
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10FAQ
What does codex-bug do?
Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, o...
When should I use codex-bug?
Invoke when Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as veri.
Is codex-bug safe to install?
Review the Security Audits panel on this page before installing in production.