superdocs

Generates a comprehensive docs/ directory from git history, code, and plans.

3|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/asteroid-belt/skills --skill superdocs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superdocs
Source: https://github.com/asteroid-belt/skills/tree/main/skills/superdocs
Command: npx skills add https://github.com/asteroid-belt/skills --skill superdocs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claude, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Generates a comprehensive docs/ directory that explains WHAT a codebase is, HOW it works, and WHY decisions were made, enabling AI agents and humans to understand and contribute without starting from scratch. It detects monorepos, supports re-running to refresh outdated content, and runs automatically without user prompts.

Core Features & Use Cases

  • Scans any codebase (single repo or monorepo) to produce structured markdown docs.
  • Generates: overview.md, architecture.md, getting-started.md, development.md, adr/ (index and individual ADRs), glossary.md.
  • Detects stale content and re-runs to update changed areas; centralizes existing ADRs into docs/adr/.
  • Works offline and in CI, with templates and references to support customization.

Quick Start

Run the included script from the project root to generate the full docs/ set.

Frequently Asked Questions about superdocs

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

FAQPage Schema
How do I automatically generate codebase documentation for a monorepo?

To automatically generate codebase documentation for a monorepo, you can run a script from the project root that scans the codebase and produces a structured markdown docs/ directory. It detects monorepos and synthesizes architecture and overview files without manual prompts.

What is the best way to keep codebase documentation updated as the code evolves?

The best way to keep codebase documentation updated is to use a tool that detects stale content and re-runs to refresh only the changed areas. This produces living documentation that stays current by synthesizing evidence from git history and code.

How does automatic codebase documentation handle architectural decision records?

Automatic codebase documentation handles architectural decision records by generating an adr/ directory with an index and individual ADRs. It centralizes existing ADRs into the docs/ folder to explain why specific technical decisions were made.

Can I generate codebase docs offline or in a CI pipeline?

Yes, you can generate codebase docs offline and in CI pipelines. The documentation generation process runs automatically without user prompts and includes templates and references to support customization in automated environments.

What files are included when generating a comprehensive docs directory?

Generating a comprehensive docs directory produces structured markdown files including overview.md, architecture.md, getting-started.md, development.md, a glossary.md, and an adr/ folder. These files explain what the codebase does and how it is structured.