Receber por email
← Voltar para o catálogo

openapi-spec-generator

Automated OpenAPI specification generation from code annotations, comments, and interface definitions

1.4kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add a5c-ai/babysitter

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/openapi-spec-generator/svg)](https://www.skillteca.com.br/skills/openapi-spec-generator)

Skills relacionadas

Ver todas de Automação →

Alerta por categoria

Receba novas skills de Automação toda segunda

1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

OpenAPI Spec Generator Skill

Overview

This skill automates the generation of OpenAPI 3.x specifications from code annotations, comments, and interface definitions. It parses source code to extract API endpoints, schemas, and documentation to produce comprehensive and accurate API specifications.

Capabilities

  • Parse code to extract API endpoints and schemas from annotations
  • Generate OpenAPI 3.x specifications in YAML or JSON format
  • Validate spec completeness and correctness against OpenAPI standards
  • Auto-update specs from code changes with incremental generation
  • Support multiple frameworks (Express, FastAPI, Spring, ASP.NET, etc.)
  • Extract request/response schemas from TypeScript types, Python type hints, Go structs
  • Generate examples from code-level documentation

Target Processes

  • API Design Specification
  • API Documentation System
  • SDK Code Generation Pipeline

Integration Points

  • Code analysis tools (AST parsers)
  • Schema validators (Spectral, openapi-spec-validator)
  • Swagger/OpenAPI tooling ecosystem
  • IDE extensions for spec preview

Input Requirements

  • Source code with API route definitions
  • Annotation/decorator conventions used in the codebase
  • Target OpenAPI version (3.0.x or 3.1.x)
  • Output format preference (YAML/JSON)

Output Artifacts

  • OpenAPI specification file (openapi.yaml or openapi.json)
  • Validation report with any issues found
  • Schema extraction summary
  • Change diff from previous spec version (if applicable)

Usage Example

skill:
  name: openapi-spec-generator
  context:
    sourceDirectory: ./src/api
    framework: express
    outputFormat: yaml
    openapiVersion: "3.1.0"
    includeExamples: true

Best Practices

  1. Use consistent annotation patterns across the codebase
  2. Include JSDoc/docstrings for all endpoints
  3. Define reusable schema components
  4. Validate generated specs before publishing
  5. Version control generated specifications
Compartilhar X LinkedIn