DOWNLOADABLE CODEX SKILL · v1.0.0
Turn a vague bug report into the smallest repeatable failure with captured evidence.
By Abdessalam · Updated
THE WORKFLOW
Turn a vague bug report into the smallest repeatable failure with captured evidence. It keeps the work tied to evidence and the project’s actual constraints.
The user asks to reproduce, confirm, or narrow a software defect. Download the package, inspect its instructions, and adapt its review notes to the project.
EXAMPLE REQUEST
$aboutcodex-reproduce-issue Reproduce the mobile overflow on this WordPress archive and isolate the responsible component.A minimal reproduction with evidence and the remaining variables.
Inspect the extracted package first. For a local project, place the skill folder here:
.agents/skills/aboutcodex-reproduce-issue/SKILL.mdOpen the project and inspect the Skills sidebar to locate the skill by name. Follow the skill controls available in your current desktop application.
Open the project in Codex CLI. Use /skills or $aboutcodex-reproduce-issue to select the skill explicitly.
Open the project in the Codex IDE extension. Use /skills or $aboutcodex-reproduce-issue to select the skill explicitly.
Verify discovery: locate the exact skill name before starting. If missing, check the folder, SKILL.md filename, and name/description frontmatter, then restart the client.
After selecting the skill, use this inspection request:
Read the aboutcodex-reproduce-issue skill. Explain its purpose, inputs, and boundaries. Do not edit files or run its workflow yet.Documentation-based guidance, checked September 10, 2026. Client discovery was not independently tested here. OpenAI’s skill documentation. Troubleshoot installation
aboutcodex-reproduce-issue/SKILL.md1 KBaboutcodex-reproduce-issue/references/NOTES.md419 Baboutcodex-reproduce-issue/LICENSE.txt1 KB---
name: "aboutcodex-reproduce-issue"
description: "Turn a vague bug report into the smallest repeatable failure with captured evidence. Use when the user asks to reproduce, confirm, or narrow a software defect."
---
# Reproduce a reported issue
Turn a vague bug report into the smallest repeatable failure with captured evidence.
## Workflow
1. Preserve the original report and separate observations from assumptions.
2. Identify the environment, starting state, input, action, and expected result.
3. Reduce the path while keeping the failure, changing one variable at a time.
4. Capture the first useful error, visible symptom, or state difference without exposing secrets.
5. Write a deterministic reproduction or state why the issue could not be reproduced.
Read `references/NOTES.md` before finalizing the work. Follow project instructions and the user's authorized scope. Use available evidence, label assumptions, and never report a check as passing unless it actually ran.
## Deliverable
A minimal reproduction with evidence and the remaining variables. State material limitations and link to changed files or rendered evidence when available.
A missing account, dataset, device, or private service can prevent faithful reproduction.
Structure checked · 2026-09-10
Required frontmatter, folder layout, file inventory, validator run, and generated ZIP round-trip checked. Workflow behavior has not been independently evaluated.
Package checks confirm file structure. They do not establish that a skill works well on every task.
1.0.0 — Initial instruction-only release with supporting review notes.
Progress stays in this browser. No account needed.
Added interface-specific guidance and a read-only inspection request. The downloadable package is unchanged.
What to do: No re-download needed for this documentation update. Inspect the current version and compare your local changes before replacing a skill.
This log starts with the first recorded review; it is not a reconstruction of earlier revisions.
THE ABOUTCODEX BRIEFING
One workflow to try, one change explained, and one resource to keep. Planned weekly.
Read the sample issue ↗Confirm your email to join. Unsubscribe anytime through a delivered newsletter. Privacy policy.