api-documenting
The api-documenting skill generates comprehensive API documentation by extracting endpoint information from source code, including HTTP methods, routes, parameters, schemas, and authentication requirements. Use this skill when documenting REST APIs, creating API references, generating endpoint documentation, or producing OpenAPI/Swagger specifications for both markdown and specification formats.
git clone --depth 1 https://github.com/huangjia2019/claude-code-engineering /tmp/api-documenting && cp -r /tmp/api-documenting/04-Skills/projects/02-progressive-skill ~/.claude/skills/api-documentingSKILL.md
# API Documentation Generator Generate comprehensive API documentation from source code. ## Quick Reference For common documentation patterns, see `PATTERNS.md`. ## Documentation Standards See `STANDARDS.md` for our documentation conventions. ## Process ### Step 1: Identify API Endpoints Look for: - Route definitions (Express, FastAPI, etc.) - Controller methods - Handler functions ### Step 2: Extract Information For each endpoint, extract: - HTTP method (GET, POST, PUT, DELETE, etc.) - Path/route - Parameters (path, query, body) - Request/response schemas - Authentication requirements ### Step 3: Generate Documentation Use the template in `templates/endpoint.md` for consistent formatting. ### Step 4: Create Overview Generate an index of all endpoints with the template in `templates/index.md`. ## Output Formats ### Markdown (Default) Generate markdown documentation suitable for README or docs site. ### OpenAPI/Swagger If requested, generate OpenAPI 3.0 spec. See `templates/openapi.yaml` for structure. ## Examples See `EXAMPLES.md` for sample inputs and outputs. ## Scripts To auto-detect routes in common frameworks: ```bash python scripts/detect_routes.py <source_directory> ``` To validate generated OpenAPI spec: ```bash ./scripts/validate_openapi.sh <spec_file> ```
Review code changes for quality, security, and best practices. Proactively use this after code modifications.
Run tests and report results concisely. Use this after code changes to verify everything works.
Analyze log files and extract actionable insights. Use when troubleshooting issues or investigating incidents.
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
Explore and analyze authentication-related code. Use when investigating auth flows, session management, or security.
Explore and analyze database-related code. Use when investigating data models, queries, or persistence.
Analyze root cause of bugs after location is identified. Second step in bug investigation.
Implement bug fixes after analysis is complete. Third step in bug fix pipeline.