api-doc

Sync FastAPI endpoint routes with API reference documentation.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/jrmatherly/apollos-portal --skill api-doc-jrmatherly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-doc
Source: https://github.com/jrmatherly/apollos-portal/tree/main/.claude/skills/api-doc
Command: npx skills add https://github.com/jrmatherly/apollos-portal --skill api-doc-jrmatherly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync API reference documentation with the actual FastAPI routes to prevent drift between code and docs, saving time during refactors.

Core Features & Use Cases

  • Extracts all routes from backend/app/api/v1/endpoints by scanning decorators like @router.get, @router.post, @router.patch, and their path and response models.
  • Compares the discovered endpoints against docs/api-reference/introduction.mdx and reports any discrepancies.
  • Updates the docs table and related reference pages to reflect the current API surface.

Quick Start

Run the API doc sync to align the docs with the latest backend routes.

Frequently Asked Questions about api-doc

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

FAQPage Schema
How do I sync FastAPI documentation with actual endpoint routes?

To sync FastAPI documentation with endpoint routes, the tool scans backend/app/api/v1/endpoints decorators to extract routes and response models, then compares them against docs/api-reference/introduction.mdx to report and resolve discrepancies.

How do I prevent drift between FastAPI code and API reference docs?

Preventing drift between FastAPI code and API reference docs requires comparing actual endpoint decorators against your MDX documentation files to identify missing or mismatched routes and automatically update reference pages.

What is the best way to update MDX API reference pages after refactoring endpoints?

The best way to update MDX API reference pages after refactoring endpoints is to analyze modified FastAPI route decorators, identify the changed API surface, and update endpoint tables and related docs to reflect current backend implementation.

Can I automatically detect missing endpoints in my FastAPI documentation?

You can automatically detect missing endpoints in FastAPI documentation by scanning route decorators in your endpoints directory and comparing the extracted API surface against your introduction.mdx file to flag undocumented routes.

Does this docs sync tool extract response models from FastAPI decorators?

Yes, this docs sync tool extracts response models directly from FastAPI decorators. It scans decorators like @router.get, @router.post, and @router.patch to capture paths and response models for documentation comparison.