documentation-generator

Generate API references, user guides, and changelogs from code and git history.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill documentation-generator-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-generator
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/documentation-generator
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill documentation-generator-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-generate user-facing documentation by deriving an API reference from code comments and type definitions, assembling user guides from the product spec, and generating a changelog from git history. Documentation is published as part of the website or as a separate docs site and rebuilds on every deploy.

Core Features & Use Cases

  • Generate API references from code comments and type definitions, including descriptions, parameters, and examples.
  • Produce user guides derived from the product spec, with step-by-step instructions and troubleshooting tips.
  • Generate a changelog from conventional commits and git history, with versioned sections and release notes.
  • Cross-link and publish documentation across the site, ensuring docs stay up-to-date on deploys.

Quick Start

Configure a docs site route (e.g., /docs) and run the documentation workflow as part of your deployment pipeline.

Frequently Asked Questions about documentation-generator

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

FAQPage Schema
How do I auto-generate API docs from code comments and type definitions?

To auto-generate API docs, the system analyzes TypeScript and JSDoc annotations to extract descriptions, parameters, and examples. This builds comprehensive API references directly from your codebase, ensuring documentation stays synchronized with implementation changes.

Can I generate a changelog automatically from conventional commits and git history?

Generating a changelog from git history uses conventional commits to produce versioned sections and release notes. This automation captures code changes accurately, creating structured release documentation without manual entry or editing.

How do I create user guides derived from a product spec?

Creating user guides from a product spec assembles step-by-step instructions and troubleshooting tips automatically. This translates product specifications into user-facing documentation, providing clear guidance without manual writing.

Does auto-generated documentation support publishing via a docs site on deploy?

Auto-generated documentation supports publishing via a docs site route configured in your deployment pipeline. The documentation rebuilds on every deploy, ensuring published guides and API references remain current with cross-links and versioning.

What's the best way to keep API references and user guides up-to-date across deploys?

Keeping API references and user guides up-to-date requires automated rebuilds triggered on every deploy. By deriving documentation from code comments, type definitions, and git history, the system cross-links and publishes current docs automatically.