DOWNLOADABLE CODEX SKILL · v1.0.0
Trace a failing CI job to a likely cause and the smallest useful next action.
By Abdessalam · Updated
THE WORKFLOW
Trace a failing CI job to a likely cause and the smallest useful next action. It keeps the work tied to evidence and the project’s actual constraints.
The user provides a failed pipeline, test log, or CI status that needs diagnosis. Download the package, inspect its instructions, and adapt its review notes to the project.
EXAMPLE REQUEST
$aboutcodex-ci-failure-triage Triage this failed GitHub Actions run and identify the first causal error.A cause-ranked diagnosis, focused reproduction, and verified next step where possible.
Inspect the extracted package first. For a local project, place the skill folder here:
.agents/skills/aboutcodex-ci-failure-triage/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-ci-failure-triage to select the skill explicitly.
Open the project in the Codex IDE extension. Use /skills or $aboutcodex-ci-failure-triage 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-ci-failure-triage 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-ci-failure-triage/SKILL.md1 KBaboutcodex-ci-failure-triage/references/NOTES.md465 Baboutcodex-ci-failure-triage/LICENSE.txt1 KB---
name: "aboutcodex-ci-failure-triage"
description: "Trace a failing CI job to a likely cause and the smallest useful next action. Use when the user provides a failed pipeline, test log, or CI status that needs diagnosis."
---
# Triage a CI failure
Trace a failing CI job to a likely cause and the smallest useful next action.
## Workflow
1. Identify the first meaningful failure rather than the final cascade of cancelled or dependent jobs.
2. Connect the failing command to the workflow file, runtime version, dependency state, and changed code.
3. Reproduce the narrow command locally when the environment permits.
4. Separate deterministic product failures from flaky infrastructure or credential problems.
5. Propose or implement the smallest fix, then rerun the focused check before broader jobs.
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 cause-ranked diagnosis, focused reproduction, and verified next step where possible. State material limitations and link to changed files or rendered evidence when available.
Cannot access private runner state or credentials unless the user provides authorized access.
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.