api-spec-validator

Validate endpoints, DTOs, error codes, and response formats in code against the API spec and generate a validation report.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/scit-48-1/aini-inu-backend --skill api-spec-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-spec-validator
Source: https://github.com/scit-48-1/aini-inu-backend/tree/main/.gemini/skills/api-spec-validator
Command: npx skills add https://github.com/scit-48-1/aini-inu-backend --skill api-spec-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Validate that implementation code matches the API specification to prevent drift.

Core Features & Use Cases

  • Validate endpoints align with API spec across controllers
  • Validate Request/Response DTO fields and ErrorCodes against the spec
  • Generate change reports after spec updates and provide validation outputs

Quick Start

Read the API spec, review the validation checklist, and run the validation against the target codebase to verify alignment.

Frequently Asked Questions about api-spec-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate that my code matches the API specification?

You can validate endpoints across controllers by running the Skill against your target codebase with the updated API spec to ensure request/response DTOs, error codes, and response formats align without drift.

What is API spec drift and how do I prevent it during code reviews?

API spec drift occurs when implementation code diverges from the defined API specification. You prevent it by validating endpoints, DTOs, and error codes against the spec during code reviews and before PRs.

Can I generate a change report after updating my API spec?

Yes, you can generate a change report after API spec updates by running the validation against your target codebase to verify alignment and produce a detailed validation output.

What do I need to check before submitting a PR to ensure endpoints align with the API spec?

Before submitting a PR, you need to run a validation check that compares your controllers, request/response DTO fields, and error codes against the API spec to ensure full alignment and prevent drift.

Does the API validator check response formats and DTO fields against the spec?

Yes, the API validator checks response formats, request/response DTO fields, and error codes against the API spec to ensure your implementation matches the specification without drift.