openapi-gen

Generate OpenAPI 3.0 specifications from TypeScript Express-like route definitions.

11|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/berkcangumusisik/claude-code-practices --skill openapi-gen-berkcangumusisik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openapi-gen
Source: https://github.com/berkcangumusisik/claude-code-practices/tree/main/skills/openapi-gen
Command: npx skills add https://github.com/berkcangumusisik/claude-code-practices --skill openapi-gen-berkcangumusisik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate a comprehensive OpenAPI 3.0 specification from existing route definitions, helping teams document APIs quickly and keep docs in sync with code.

Core Features & Use Cases

  • Route discovery: scans source code to identify endpoints, HTTP methods, and paths.
  • Schema extraction: derives request and response shapes from validation schemas and TypeScript types.
  • Documentation generation: outputs openapi.yaml and complements inline comments for client SDKs.
  • Use Case: accelerate API onboarding and API-first development by providing a complete, up-to-date spec.

Quick Start

Run the OpenAPI generator against your project to produce openapi.yaml for your API surface.

Frequently Asked Questions about openapi-gen

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

FAQPage Schema
How do I generate an OpenAPI spec from existing Express routes?

It outputs an openapi.yaml file containing reusable components, security schemes, and derived request/response schemas, which can be directly imported into Swagger UI or used to generate client SDKs.

Can I extract OpenAPI schemas from TypeScript types and validation schemas?

It outputs an openapi.yaml file containing reusable components, security schemes, and derived request/response schemas, which can be directly imported into Swagger UI or used to generate client SDKs.

Does this approach work with TypeScript backend projects for Swagger documentation?

It outputs an openapi.yaml file containing reusable components, security schemes, and derived request/response schemas, which can be directly imported into Swagger UI or used to generate client SDKs.

What's the best way to keep OpenAPI documentation in sync with code?

It outputs an openapi.yaml file containing reusable components, security schemes, and derived request/response schemas, which can be directly imported into Swagger UI or used to generate client SDKs.