ABOUTCODEX / TROUBLESHOOTING
Find help by the symptom
Start with what went wrong. Follow a focused check and a connected guide.
START WITH THE SYMPTOM
Skill does not appear
Check the extracted folder, exact SKILL.md filename, and frontmatter. Compare your setup with the installation guide.
Follow the troubleshooting guide →START WITH THE SYMPTOM
Skill runs for the wrong task
Compare the request with the skill description. Use a narrow explicit request and check which procedure was selected.
Follow the troubleshooting guide →START WITH THE SYMPTOM
Codex cannot find my files
Confirm the working folder and the exact file path. Ask for a read-only inventory before changing files.
Follow the troubleshooting guide →START WITH THE SYMPTOM
The task keeps expanding
Restate the outcome, allowed files, and acceptance criteria. Review the proposed change before proceeding.
Follow the troubleshooting guide →START WITH THE SYMPTOM
A workflow has stalled
Record the last completed step, failing command, and missing information. Reduce the problem to one observable check.
Follow the troubleshooting guide →START WITH THE SYMPTOM
Instructions conflict
Locate the applicable project instructions and identify the precise conflict. Avoid adding another broad rule.
Follow the troubleshooting guide →START WITH THE SYMPTOM
WordPress layout breaks on mobile
Inspect the page at a narrow width and identify whether the block, theme, or custom CSS owns the failing dimensions.
Follow the troubleshooting guide →START WITH THE SYMPTOM
The fix works once but fails again
Reproduce the sequence with a small fixture. Add a regression check for repeated calls and verify the same test before and after.
Follow the troubleshooting guide →