-
Resolve target spec — Follow _shared/resolve-api-spec.md. Print **Target spec:** \path`` in the output header.
-
Layer 1 — Redocly lint — Run:
npm run lint:openapi -- <resolved-path>
List every error/warning with path/line. Tag each as api-fix-eligible (→ fix with /api-fix).
-
Layer 2 — Structure — Load api-ref-structure.mdc. Flag section order, missing license, broken $ref, duplicate schema names. Tag as api-fix-eligible.
-
Layer 3 — OpenAPI version — Read openapi field. Audit 3.0 vs 3.1 rules per api-ref-schema.mdc ($ref, type arrays, anyOf/null). Flag issues lint may miss.
-
Layer 4 — FFS style guide — Load api-ref-ffs-styleguide.mdc and ffs-styleguide-checklist.md. Flag significant contract inconsistencies only.
-
Layer 5 — Documentation — Load api-ref-copy, api-ref-examples, api-ref-tags-errors. Check descriptions, examples, tags, public-facing text (no Jira/FFENT/codenames).
-
Output format
- Summary — counts by layer and severity
- Redocly lint — numbered list (
api-fix-eligible)
- Structure — numbered list (
api-fix-eligible)
- OpenAPI version — findings
- FFS style guide — findings (wiki section if helpful)
- Documentation / copy — findings; suggest
/api-review for full catalog
- Reminder:
/api-fix = lint + api-ref-structure; copy/style = /api-review or update refs N,M,…