DOWNLOADABLE CODEX SKILL · v1.0.0
Verify that a proposed fix removes the reported failure without creating an obvious regression.
By Abdessalam · Updated
THE WORKFLOW
Verify that a proposed fix removes the reported failure without creating an obvious regression. It keeps the work tied to evidence and the project’s actual constraints.
The user asks to confirm a fix for a non-security bug. Download the package, inspect its instructions, and adapt its review notes to the project.
EXAMPLE REQUEST
$aboutcodex-fix-verification Verify the pagination fix for filtered skill-library results.A pass, fail, or blocked verdict supported by exact observations.
Inspect the extracted package first. For a local project, place the skill folder here:
.agents/skills/aboutcodex-fix-verification/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-fix-verification to select the skill explicitly.
Open the project in the Codex IDE extension. Use /skills or $aboutcodex-fix-verification 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-fix-verification 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-fix-verification/SKILL.md1 KBaboutcodex-fix-verification/references/NOTES.md430 Baboutcodex-fix-verification/LICENSE.txt1 KB---
name: "aboutcodex-fix-verification"
description: "Verify that a proposed fix removes the reported failure without creating an obvious regression. Use when the user asks to confirm a fix for a non-security bug."
---
# Verify a bug fix
Verify that a proposed fix removes the reported failure without creating an obvious regression.
## Workflow
1. Restate the original reproduction and its expected result.
2. Run the reproduction against the fixed state and capture the changed observation.
3. Add or identify a focused regression check that fails on the old behavior when feasible.
4. Exercise adjacent states that share the changed path, especially empty, error, and repeated-action cases.
5. Report the exact revision, environment, checks, and limits of verification.
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 pass, fail, or blocked verdict supported by exact observations. State material limitations and link to changed files or rendered evidence when available.
Does not establish security remediation or production health unless those were separately tested.
Workflow evaluated · 2026-09-10
Environment: Python 3.14.5; standard library unittest; isolated temporary directory; assistant manually applied skill instructions.
Python fixture: unchanged starter exits 1 with two repeated-save failures; fixed function exits 0 with all six tests passing. Same test suite verifies blank IDs, empty list, input non-mutation, ordering, and repeated calls. Full report: https://aboutcodex.com/fix-verification-skill-evaluation/ Scope is limited to the recorded exercise.
Read the full evaluation and reproduce the exercise →
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.
Python fixture: unchanged starter exits 1 with two repeated-save failures; fixed function exits 0 with all six tests passing. Same test suite verifies blank IDs, empty list, input non-mutation, ordering, and repeated calls.
What to do: Read the linked evaluation and repeat the matching exercise. Package instructions are unchanged; no re-download is required.
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.