Codex Fyzz Chat Lint and Validation Sequence
Interpret Fyzz Chat's formatting, type-check, test and build results in order and focus on the first actionable failure.
中文Install in Codex
Open Fyzz Chat in Codex with its Bun environment and the current change. Existing check results also work for a review.
- Review `.agents/skills/lint/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/lint/` in your project and save the reviewed file as `.agents/skills/lint/SKILL.md`.
- Start Codex from that project's root, then type `$lint` and select the matching skill.
Example task
Explain these sample check results and propose the next sequence.
{"format":"passed","typecheck":"failed","file":"labels.ts","tests":"not run","build":"not run"}What to check
Investigate `typecheck=failed` in `labels.ts` first. After it passes, continue with tests and build and record each result.
Original SKILL.md on GitHub · Updated
Frequently asked question
Can the formatting step change source?
The project formatter applies automated fixes. Check its changes separately from type, test and build results.