api-docs-generator
Automatically generates and updates API documentation from code changes with multiple format support
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install aegntic-claudeism-api-docs-generator
Repository
Skill path: .claude/skills/api-docs-generator
Automatically generates and updates API documentation from code changes with multiple format support
Open repositoryBest for
Primary workflow: Write Technical Docs.
Technical facets: Full Stack, Backend, Tech Writer.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: aegntic.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install api-docs-generator into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/aegntic/claudeism before adding api-docs-generator to shared team environments
- Use api-docs-generator for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: api-docs-generator description: Automatically generates and updates API documentation from code changes with multiple format support keywords: [documentation, automation, complex, weekly] --- # api-docs-generator ## What This Skill Does Automatically generates and updates API documentation from code changes with multiple format support ## Domain Focus This skill specializes in documentation with complex complexity and weekly usage patterns. ## When This Skill Auto-Triggers Claude will automatically use this skill when detecting: - Analyze code changes for documentation impact - Generate OpenAPI specifications from source code - Update Markdown documentation files - Deploy to documentation hosting - Maintain consistency across formats ## Core Capabilities ### 1. Primary Function - [Main capability based on requirements] ### 2. Integration Points - OpenAPI specification generation - Markdown documentation rendering - GitHub Pages deployment - Code analysis and parsing tools ### 3. Error Handling - Comprehensive error detection and recovery - Graceful degradation on failures - Clear error messaging and user guidance ## Usage Examples ### Example 1: Basic Usage [Brief example of primary use case] ### Example 2: Advanced Usage [Complex usage scenario with multiple features] ## Token Usage Estimated token budget: 300-400 tokens - Metadata load: ~30 tokens - Full content load: ~200-500 tokens - Context management: Optimized for weekly usage ## Best Practices - Use for documentation tasks with complex complexity - Integrate with other components for complete workflows - Monitor token usage for weekly operations ## Integration with Other Components - OpenAPI specification generation - Markdown documentation rendering - GitHub Pages deployment - Code analysis and parsing tools ## Generated: 2025-10-29