DOWNLOADABLE CODEX SKILL · v1.0.0
Build a risk-based regression plan for a change without duplicating implementation details.
By Abdessalam · Updated
THE WORKFLOW
Build a risk-based regression plan for a change without duplicating implementation details. It keeps the work tied to evidence and the project’s actual constraints.
The user asks what to test before merging or publishing a change. Download the package, inspect its instructions, and adapt its review notes to the project.
EXAMPLE REQUEST
$aboutcodex-regression-plan Create a regression plan for adding collection filters to the WordPress skill library.A prioritized, executable set of checks with clear pass evidence.
Inspect the extracted package first. For a local project, place the skill folder here:
.agents/skills/aboutcodex-regression-plan/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-regression-plan to select the skill explicitly.
Open the project in the Codex IDE extension. Use /skills or $aboutcodex-regression-plan 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-regression-plan 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-regression-plan/SKILL.md1 KBaboutcodex-regression-plan/references/NOTES.md440 Baboutcodex-regression-plan/LICENSE.txt1 KB---
name: "aboutcodex-regression-plan"
description: "Build a risk-based regression plan for a change without duplicating implementation details. Use when the user asks what to test before merging or publishing a change."
---
# Create a focused regression plan
Build a risk-based regression plan for a change without duplicating implementation details.
## Workflow
1. Describe the changed behavior, its direct consumers, and the state or data it touches.
2. Rank credible failure paths by impact and likelihood using the diff and architecture.
3. Select focused checks for the change, shared-component checks for propagation, and one critical end-to-end path.
4. Include viewport, permission, empty-state, and failure cases only where the change can affect them.
5. Define observable pass criteria and a rollback or containment signal.
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 prioritized, executable set of checks with clear pass evidence. State material limitations and link to changed files or rendered evidence when available.
A plan is not proof that checks ran; execution results must be recorded separately.
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.