ワンクリックでManusで任意のスキルを実行

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.

Manusで実行

スター90,015

フォーク13,263

更新日2026年4月8日 02:20

ソース

openai

openai/codex

GitHub リポジトリを開く Creator のリポジトリを見る

インストールコマンド

ダウンロード

Manusで実行

役立つ用途SOC

ソフトウェア品質保証アナリスト・テスターコンピュータ・数学職15-1253L4

SKILL.md

readonly

name	codex-bug
description	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.

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

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.

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.

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.

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.

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).

Respond

Provide a concise report of your findings and next steps.

このリポジトリの他の Skills

同じリポジトリ

babysit-pr

openai/codex

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

2026-06-0990.0k

pushing-ci-changes

openai/codex

Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.

2026-06-0490.0k

codex-pr-body

openai/codex

Update the title and body of one or more pull requests.

2026-06-0390.0k

openai-docs

openai/codex

Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.

2026-05-2890.0k

plugin-creator

openai/codex

Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.

2026-05-2090.0k

update-v8-version

openai/codex

Update Codex's pinned `v8` / `rusty_v8` versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update `rusty_v8` artifacts, prepare or validate a V8 release candidate, check `v8-canary`, or diagnose why a V8 version update no longer builds.

2026-05-1990.0k

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

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.

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.

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.

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.

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).

Respond

Provide a concise report of your findings and next steps.