Codex Musi Compiler Diagnostics for Return Type Mismatches
Write compiler messages that name the subject and expected type, label the offending span and use a secondary location when available.
中文Install in Codex
Open Musi in Codex with the diagnostic kind for this phase, source spans and test fixtures.
- Review `.agents/skills/musi-diagnostics/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/musi-diagnostics/` in your project and save the reviewed file as `.agents/skills/musi-diagnostics/SKILL.md`.
- Start Codex from that project's root, then type `$musi-diagnostics` and select the matching skill.
Example task
Draft a compiler diagnostic and span placement from this illustrative return mismatch.
{"site":"return value","expected":"Bool","found":"Float","primaryLine":12,"declarationLine":3}What to check
Use `return value expected Bool, found Float`. Mark line `12` as primary and line `3` as a secondary declaration location if available.
Original SKILL.md on GitHub · Updated
Frequently asked question
When can a diagnostic offer an automatic fix?
Offer a fix only when the replacement is exact and safe. Explain the type mismatch when several edits are possible.