TypingMindTypingMindThe best frontend for AI
Codex Bug logo

Codex Bug

Community
deonmenezes
codex-bug

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.

Overview

Publisherdeonmenezes
Repositorymantishack
Skill namecodex-bug
Stars
503
Forks
75
Bundled files
Instructions only
LicenseApache-2.0
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by deonmenezes on GitHub. Read the source before you install it.

Installation

Install the Codex Bug AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/deonmenezes/mantishack/tree/main/.codex/skills/codex-bug
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/deonmenezes/mantishack.git /tmp/mantishack
mkdir -p .claude/skills
cp -r /tmp/mantishack/.codex/skills/codex-bug .claude/skills/codex-bug
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Codex Bug in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Codex Bug on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Codex Bug is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.
  1. 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.
  1. 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.
  1. 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.
  1. 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).
  1. Respond
  • Provide a concise report of your findings and next steps.

Frequently asked questions

What does the Codex Bug AI skill 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, or explaining why it is not a bug; follow any additional user-provided instructions.

Why use Codex Bug on TypingMind?

Because you install it once and use it with any model. Codex Bug is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Codex Bug in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/deonmenezes/mantishack/tree/main/.codex/skills/codex-bug. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Codex Bug?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Codex Bug?

As many as you like. As long as a model supports skills, you can use Codex Bug with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Codex Bug AI skill free?

Yes. It is published on GitHub by deonmenezes under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
vercel logo

Gh Stack

vercel
OrganizationPopular

Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or…

34.7K
143.1K
3 files
View
openclaw logo

Agent Transcript

openclaw
OrganizationPopular

Requested GitHub PR/issue agent transcripts: redact, trim, preview, and insert safely.

82.2K
391K
1 files
View
openclaw logo

Openclaw Refactor Docs

openclaw
OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

82.2K
391K
Instructions
View
openclaw logo

Gemini

openclaw
OrganizationPopular

Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.

82.2K
391K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇