api-generating
This Claude Code skill generates API endpoint documentation from Express.js route files by running a Python detection script to discover routes, analyzing each route's HTTP method, parameters, and middleware requirements, then producing formatted markdown documentation using a standardized template. Use it when developers need to create, update, or audit API documentation for Express.js applications, ensuring comprehensive coverage of authentication and validation requirements.
git clone --depth 1 https://github.com/huangjia2019/claude-code-engineering /tmp/api-generating && cp -r /tmp/api-generating/04-Skills/projects/06-agent-skill-combo/.claude/skills/api-generating ~/.claude/skills/api-generatingSKILL.md
# API 文档生成 Skill ## 工作流程 — MANDATORY **IMPORTANT**: You MUST follow these steps in order. DO NOT skip or substitute any step. ### Step 1: Route Discovery(路由发现) **You MUST use the Python script for route detection:** ```bash python3 skills/scripts/detect-routes.py src/ ``` DO NOT manually search for routes using Grep — the script handles edge cases (dynamic routes, middleware-mounted sub-routers, re-exported routes) that Grep patterns will miss. ### Step 2: Route Analysis(路由分析) For each route discovered by the script: 1. Read the route handler source file 2. Identify: HTTP method, path, parameters, request body schema, response schema 3. Check for authentication middleware (e.g., `requireAuth`, `isAdmin`) 4. Check for validation middleware (e.g., `validate(schema)`) ### Step 3: Documentation Generation(文档生成) Use the template at `templates/api-doc.md` to generate documentation. **Output rules:** - One markdown file per route group (e.g., `docs/api/users.md`) - Include request/response examples - Mark authenticated endpoints with 🔒 ## Reference Files - Route detection script: `scripts/detect-routes.py` - Documentation template: `templates/api-doc.md` - Express routing patterns: see PATTERNS.md (same directory) ## Quality Checklist Before finishing, verify: - [ ] All routes from script output are documented - [ ] Request/response schemas match actual code - [ ] Auth requirements are marked - [ ] Examples are valid JSON
Deep analysis of code against project standards
API design patterns and conventions for this project. Covers RESTful URL naming, response format standards, error handling, and authentication requirements. Use when writing or reviewing API endpoints, designing new APIs, or making decisions about request/response formats.
Generate comprehensive API documentation by scanning Express route files.
Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.
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.
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.