api-documentation-generator

Generate structured API documentation from OpenAPI specs and code comments.

142|14|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill api-documentation-generator-arabelatso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-documentation-generator
Source: https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/api-documentation-generator
Command: npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill api-documentation-generator-arabelatso

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive API documentation by analyzing code, docstrings, and specification files, reducing manual effort and ensuring accuracy.

Core Features & Use Cases

  • Multi-Source Analysis: Extracts information from OpenAPI/Swagger specs, code comments (docstrings, JSDoc, Javadoc), and existing markdown documentation.
  • Structured Output: Organizes generated documentation into a logical multi-file structure (e.g., README, endpoints, models, errors).
  • Use Case: You have a new REST API built with FastAPI. Use this Skill to automatically generate a complete API reference guide, including endpoints, request/response schemas, and code examples, directly from your codebase and any OpenAPI specification.

Quick Start

Use the api-documentation-generator skill to create API documentation for the current repository.

Frequently Asked Questions about api-documentation-generator

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

FAQPage Schema
How do I generate API documentation from OpenAPI and Swagger specs?

You can generate API documentation by parsing OpenAPI specifications, existing markdown files, and code comments. The tool extracts endpoints, data models, and errors to organize them into a structured, multi-file reference guide automatically.

Can I generate API docs from code comments and docstrings?

Yes, API documentation can be generated directly from code comments like JSDoc, Javadoc, and docstrings. The parser extracts inline documentation from your codebase and merges it with your OpenAPI specifications to ensure comprehensive coverage.

What's the best way to document a REST API with missing or incomplete specs?

To document an API with missing specs, use a generator that handles incomplete information by cross-referencing code comments and existing markdown files. It consolidates available data to produce a structured output covering endpoints and data models despite gaps.

Does the API documentation generator work with GraphQL APIs?

Yes, the API documentation generator handles various API types including both REST and GraphQL. It parses available specifications and code comments to produce a structured, multi-file format covering overviews, endpoints, data models, and error references.

How do I structure generated API documentation into multiple files?

Generated API documentation is structured into a logical multi-file format by organizing extracted information into separate files for the README, endpoints, data models, and error references. This ensures the final output is easy to navigate and maintain.