
Documentation Generation Doc Generate
Generate API, architecture, code, and user documentation from the codebase with CI-friendly automation for solo-maintained products.
Overview
Documentation-generation-doc-generate is an agent skill most often used in build (also ship and launch) that analyzes a codebase and produces API, architecture, code, and user documentation with optional CI automation.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill documentation-generation-doc-generateWhat is this skill?
- Five documentation tracks: API, architecture, code, user guides, and automation
- Extracts endpoints and schemas into OpenAPI/Swagger with interactive UI targets
- Architecture outputs include Mermaid or PlantUML diagrams and dependency flows
- Code track covers docstrings, README setup, env vars, and troubleshooting
- CI/CD hooks for linting, coverage checks, and doc deployment
- 5 documentation workstreams: API, architecture, code, user, automation
Adoption & trust: 465 installs on skills.sh; 40.1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your product works in production but lacks accurate API specs, architecture context, and onboarding docs, so every launch or integration costs extra explanation time.
Who is it for?
Solo builders shipping APIs or SaaS who need OpenAPI, README, and user docs generated systematically from real code.
Skip if: Greenfield repos with no code to analyze yet, or teams that only need a one-line changelog entry.
When should I use this skill?
User or project needs comprehensive documentation generated from codebase analysis including API specs, diagrams, README, user guides, or doc CI.
What do I get? / Deliverables
You leave the repo with generated OpenAPI or Swagger assets, diagram-backed architecture notes, enriched README and docstrings, user guides, and a path to automated doc publishing in CI.
- OpenAPI or Swagger specification
- Architecture diagrams and dependency notes
- README and inline docstrings
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Documentation generation sits in build/docs as the primary shelf because it produces repo artifacts, though it supports ship review and launch discoverability. docs is where OpenAPI specs, READMEs, architecture diagrams, and user guides belong in the journey taxonomy.
Where it fits
Derive route handlers into an OpenAPI spec with auth and rate-limit sections.
Produce README setup, env var tables, and troubleshooting from existing config.
Refresh architecture diagrams before external code review.
Publish getting-started guides that support searchable long-tail integrator queries.
How it compares
Treat as a doc factory playbook from the repo, not a hosted documentation SaaS you install separately.
Common Questions / FAQ
Who is documentation-generation-doc-generate for?
Indie developers and small teams who maintain their own repo and want agent-driven API, architecture, code, and user documentation without a dedicated docs team.
When should I use documentation-generation-doc-generate?
Use it while building or stabilizing an API or app, before ship review when contracts must be clear, and at launch when SEO and integrators need accurate public docs.
Is documentation-generation-doc-generate safe to install?
It implies reading the codebase and possibly CI configuration; check the Security Audits panel on this page and scope network deploy steps to trusted hosts.
SKILL.md
READMESKILL.md - Documentation Generation Doc Generate
# Automated Documentation Generation Implementation Playbook This file contains detailed patterns, checklists, and code samples referenced by the skill. ## Instructions Generate comprehensive documentation by analyzing the codebase and creating the following artifacts: ### 1. **API Documentation** - Extract endpoint definitions, parameters, and responses from code - Generate OpenAPI/Swagger specifications - Create interactive API documentation (Swagger UI, Redoc) - Include authentication, rate limiting, and error handling details ### 2. **Architecture Documentation** - Create system architecture diagrams (Mermaid, PlantUML) - Document component relationships and data flows - Explain service dependencies and communication patterns - Include scalability and reliability considerations ### 3. **Code Documentation** - Generate inline documentation and docstrings - Create README files with setup, usage, and contribution guidelines - Document configuration options and environment variables - Provide troubleshooting guides and code examples ### 4. **User Documentation** - Write step-by-step user guides - Create getting started tutorials - Document common workflows and use cases - Include accessibility and localization notes ### 5. **Documentation Automation** - Configure CI/CD pipelines for automatic doc generation - Set up documentation linting and validation - Implement documentation coverage checks - Automate deployment to hosting platforms ### Quality Standards Ensure all generated documentation: - Is accurate and synchronized with current code - Uses consistent terminology and formatting - Includes practical examples and use cases - Is searchable and well-organized - Follows accessibility best practices ## Reference Examples ### Example 1: Code Analysis for Documentation **API Documentation Extraction** ```python import ast from typing import Dict, List class APIDocExtractor: def extract_endpoints(self, code_path): """Extract API endpoints and their documentation""" endpoints = [] with open(code_path, 'r') as f: tree = ast.parse(f.read()) for node in ast.walk(tree): if isinstance(node, ast.FunctionDef): for decorator in node.decorator_list: if self._is_route_decorator(decorator): endpoint = { 'method': self._extract_method(decorator), 'path': self._extract_path(decorator), 'function': node.name, 'docstring': ast.get_docstring(node), 'parameters': self._extract_parameters(node), 'returns': self._extract_returns(node) } endpoints.append(endpoint) return endpoints def _extract_parameters(self, func_node): """Extract function parameters with types""" params = [] for arg in func_node.args.args: param = { 'name': arg.arg, 'type': ast.unparse(arg.annotation) if arg.annotation else None, 'required': True } params.append(param) return params ``` **Schema Extraction** ```python def extract_pydantic_schemas(file_path): """Extract Pydantic model definitions for API documentation""" schemas = [] with open(file_path, 'r') as f: tree = ast.parse(f.read()) for node in ast.walk(tree): if isinstance(node, ast.ClassDef): if any(base.id == 'BaseModel' for base in node.bases if hasattr(base, 'id')): schema = { 'name': node.name, 'description': ast.get_docstring(node), 'fields': [] } for item in node.body: if isinstance(item, ast.AnnAssign): field = { 'nam