openapi-generator

Generate OpenAPI 3.0/3.1 specs from Express, Next.js, Fastify, or NestJS routes.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Camilo8902/GabyCosmetics --skill openapi-generator-camilo8902
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openapi-generator
Source: https://github.com/Camilo8902/GabyCosmetics/tree/main/.claude/skills/openapi-generator
Command: npx skills add https://github.com/Camilo8902/GabyCosmetics --skill openapi-generator-camilo8902

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @babel/parser, @fastify/swagger, @nestjs/swagger, commander, js-yaml, @apidevtools/swagger-parser, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of OpenAPI 3.0/3.1 specifications directly from your API codebase, eliminating manual documentation and ensuring accuracy.

Core Features & Use Cases

  • Automated Spec Generation: Creates comprehensive OpenAPI specs from Express, Next.js, Fastify, or NestJS routes.
  • Schema & Example Inclusion: Automatically extracts types to generate schemas and includes examples for clarity.
  • Use Case: When you've just finished building a new set of API endpoints, use this Skill to instantly generate a Swagger/OpenAPI documentation file that can be imported into tools like Postman or viewed with Swagger UI.

Quick Start

Use the openapi-generator skill to create an OpenAPI 3.1 specification from your Express API source code located in the './src' directory and save it to './openapi.yaml'.

Frequently Asked Questions about openapi-generator

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

FAQPage Schema
How do I generate OpenAPI specifications from Express or NestJS source code?

You can generate OpenAPI specifications by scanning your Express, Next.js, Fastify, or NestJS API routes. This process automatically extracts TypeScript types and parses JSDoc to create complete schemas, examples, and documentation for your API.

Can I create Swagger documentation from existing TypeScript API routes?

Yes, Swagger documentation is created by converting TypeScript types and parsing JSDoc metadata from your existing API routes. It produces an OpenAPI 3.0 or 3.1 specification file that can be directly imported into Swagger UI.

Does this openapi-generator work with Fastify and Next.js frameworks?

Yes, openapi-generator supports Fastify and Next.js frameworks, alongside Express and NestJS. It analyzes your API route definitions across these frameworks to automatically generate comprehensive OpenAPI 3.0/3.1 specifications.

What is the best way to automate API documentation for a TypeScript codebase?

The best way to automate API documentation is generating OpenAPI specs directly from your TypeScript codebase. By extracting schemas and parsing JSDoc route metadata, it eliminates manual documentation and ensures your API spec remains accurate.

Can I import the generated OpenAPI spec into Postman or Insomnia?

Yes, the generated OpenAPI 3.0/3.1 specifications can be imported into Postman or Insomnia. The output file contains complete schemas and examples, making it immediately compatible with these API testing platforms.

How does TypeScript type conversion work when generating API specs?

TypeScript type conversion works by automatically extracting type definitions from your API codebase and translating them into OpenAPI schemas. This ensures your generated API documentation accurately reflects your code's data structures and route parameters.