api-docs

FastAPI OpenAPI documentation requires adding response_model, status_code, tags, descriptions, and Pydantic examples to routes. This Skill audits your codebase, detects project conventions, and retrofits missing OpenAPI fields without overwriting existing documentation.

Generating Postman collection entries from FastAPI routes requires documenting endpoints with response schemas and examples. This Skill automatically scaffolds Postman collection entries for API testing and export workflows when a postman-integration skill is available.

Pydantic version detection ensures FastAPI model documentation adapts edits to your project conventions. By identifying the Pydantic version, the process correctly updates or scaffolds Field descriptions and examples according to the specific version syntax.

Yes, this documentation approach preserves existing FastAPI docstrings and field descriptions. When retrofitting endpoints to add missing OpenAPI fields, it specifically avoids overwriting any documentation already present in your codebase.

Yes, you can audit FastAPI codebases for missing response_model and error responses. The auditing process scans route files to detect missing OpenAPI fields, status codes, and Pydantic examples, then updates routers as needed to ensure API consistency.