api-documentation

Generate OpenAPI-compatible specs from source code for REST and GraphQL APIs.

42|9|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/drvoss/everything-copilot-cli --skill api-documentation-drvoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-documentation
Source: https://github.com/drvoss/everything-copilot-cli/tree/main/skills/documentation/api-documentation
Command: npx skills add https://github.com/drvoss/everything-copilot-cli --skill api-documentation-drvoss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often drifts from implementation as APIs evolve. This skill automatically generates accurate API documentation from source code to keep docs synchronized with the codebase.

Core Features & Use Cases

  • Code-driven API docs: Generate endpoint definitions, request/response formats, and authentication details from your source files.
  • OpenAPI/Swagger alignment: Produce OpenAPI-compatible specs that reflect the current implementation.
  • Onboarding support: Quickly bring new developers up to speed with current API surfaces.

Quick Start

Run the API documentation generator against your codebase to produce up-to-date OpenAPI specs.

Frequently Asked Questions about api-documentation

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

FAQPage Schema
How do I generate API documentation from source code automatically?

API documentation generation analyzes your route definitions, handler implementations, and framework conventions to produce accurate, maintainable docs that reflect current endpoints and behaviors.

Can I create an OpenAPI or Swagger spec from my existing codebase?

Yes, you can generate OpenAPI-compatible Swagger specifications directly from existing code by examining route definitions and handler implementations to ensure the spec reflects the current implementation.

Does automated API documentation work with both REST and GraphQL APIs?

Automated API documentation works with both REST and GraphQL APIs by analyzing source code to extract current endpoints, request and response formats, and authentication details.

What's the best way to keep API docs synchronized with implementation as APIs evolve?

Code-driven documentation generation keeps your API docs synchronized by automatically producing endpoint definitions and behaviors directly from your source files, preventing documentation drift.

How do I onboard new developers with up-to-date API surfaces quickly?

Generate API documentation from your source code to quickly bring new developers up to speed with current API surfaces, request and response formats, and authentication details.