Documentation Generation

Generate API references, architecture diagrams, and changelogs from source code.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill documentation-generation-strategicmilk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Documentation Generation
Source: https://github.com/StrategicMilk/Vetinari-Orchestrastor/tree/main/vetinari/skills/catalog/worker/documentation-generation
Command: npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill documentation-generation-strategicmilk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation Generation eliminates the manual burden of creating and maintaining API references, architecture diagrams, and changelogs by extracting context from code and enforcing consistent formatting.

Core Features & Use Cases

  • Generate API docs from code signatures and docstrings with consistent formatting.
  • Produce architecture docs including component diagrams and data flows, aligned with project context.
  • Create changelogs and inline docstrings following Google-style standards and project conventions.
  • Ensure accuracy via cross-checks against code and enforce style guidelines.

Quick Start

Run the Documentation Generation workflow on your codebase to produce API docs, architecture docs, and changelog entries.

Frequently Asked Questions about Documentation Generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate API docs from code signatures and docstrings automatically?

Generate API docs from code by running an automated workflow that extracts signatures and docstrings, cross-checks them against actual code, and enforces consistent formatting across API surfaces.

How do I produce architecture diagrams and data flow documentation from a codebase?

Produce architecture diagrams and data flows from a codebase by extracting project context, generating component diagrams aligned with your software structure, and ensuring architecture views match the actual code.

What is the best way to create changelogs and inline docstrings following Google-style standards?

Create changelogs and inline docstrings following Google-style standards by applying an automated generation workflow that enforces project conventions and outputs machine-checkable formats with strict style compliance.

Can I use automated documentation generation for large software projects?

Yes, automated documentation generation applies to software projects of any size, requiring consistent docs across API references, architecture views, and release notes.

How does code analysis ensure accuracy and style compliance in generated documentation?

Code analysis ensures accuracy and style compliance by cross-checking extracted documentation against actual code, enforcing style guidelines, and outputting machine-checkable formats that align with project conventions.

Why do I need to cross-check generated documentation against actual code?

Cross-check generated documentation against actual code to eliminate manual errors, ensuring API references and architecture diagrams accurately reflect the current software project context and structure.