api-swagger-doc

Generate OpenAPI 3.0 specification fragments from route handler code comments.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/CaptainPhantasy/floyd-v5 --skill api-swagger-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-swagger-doc
Source: https://github.com/CaptainPhantasy/floyd-v5/tree/main/extensibility/skills/documentation/api-swagger-doc
Command: npx skills add https://github.com/CaptainPhantasy/floyd-v5 --skill api-swagger-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate OpenAPI specifications from annotated code, ensuring API docs stay in sync with implementations.

Core Features & Use Cases

  • Scan route handlers and produce OpenAPI 3.0 specification fragments.
  • Infer paths, operations, and schemas from comments, annotations, and metadata.
  • Use in CI/CD to keep API documentation up to date as code evolves.

Quick Start

Run the tool on your codebase to generate OpenAPI fragments from your route handlers.

Frequently Asked Questions about api-swagger-doc

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

FAQPage Schema
How do I generate OpenAPI specifications from code comments in route handlers?

To generate OpenAPI specifications from code comments, this Skill parses route metadata and annotations from your backend route handlers to assemble OpenAPI 3.0 specification fragments. It outputs standalone spec snippets that keep your API documentation synchronized with your implementation.

What is the best way to keep API documentation up to date as my codebase evolves?

Keeping API documentation up to date is achieved by scanning annotated code comments in your route handlers to automatically produce OpenAPI 3.0 specification fragments. You can integrate this process into your CI/CD pipeline to ensure docs stay in sync as the code evolves.

Can I infer paths and schemas from route handler annotations for my API docs?

Yes, you can infer paths, operations, and schemas from comments, annotations, and metadata within your route handlers. The tool extracts this route metadata to assemble OpenAPI 3.0 specification fragments suitable for integration into OpenAPI tooling.

Does this approach work with backend services that have annotated endpoints across different codebases?

Yes, it is applicable to codebases with annotated endpoints across backend services. By scanning route handlers and parsing metadata from comments, it produces standalone OpenAPI specification snippets that accurately reflect your current API implementation.

What are the limitations of generating OpenAPI fragments from code comments?

Generating OpenAPI fragments from code comments requires properly annotated route handlers to infer paths and schemas. If route metadata or annotations are missing or inconsistent in the backend code, the resulting OpenAPI 3.0 specification snippets may be incomplete or inaccurate for your API docs.