openapi-review

To audit OpenAPI specs against handlers, the Skill verifies paths, HTTP verbs, and status codes against control-plane handler logic to surface semantic drift and missing details. It ensures descriptions, examples, and enum sets accurately reflect handler validation behavior.

Generated OpenAPI documentation experiences semantic drift when operation summaries and field descriptions are not derived from the actual handler code. Auditing the spec against control-plane handlers derives precise descriptions, required fields, and examples directly from implementation logic.

Yes, you can enrich OpenAPI descriptions and examples from control-plane handler code. The Skill derives precise operation summaries, per-field descriptions, valid enum values, and concrete examples directly from the handler logic while preserving generator structure and code-derived extensions.

The best way to keep OpenAPI specs aligned with handler validation is performing a semantic audit after regeneration. The Skill verifies request and response fields against handler logic, making it suitable for pre-commit checks and retroactive drift remediation to ensure continuous alignment.

Yes, the OpenAPI semantic audit preserves generator structure and code-derived extensions. While the Skill enriches operations with precise summaries, field descriptions, valid enum sets, and examples derived from handler code, it maintains the original generator structure throughout the remediation process.