doc-gen

Generate function-level, module, and API documentation from code structure.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/special-place-administrator/citadel_codex --skill doc-gen-special-place-administrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-gen
Source: https://github.com/special-place-administrator/citadel_codex/tree/main/skills/doc-gen
Command: npx skills add https://github.com/special-place-administrator/citadel_codex --skill doc-gen-special-place-administrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation is often inconsistent across codebases, requiring manual effort to align code, READMEs, and API references. This skill automates doc generation by inspecting code structure and project style, producing docs that match existing conventions.

Core Features & Use Cases

  • Detects code structure and project conventions to produce accurate, style-consistent docs.
  • Generates function-level docs, module READMEs, and API references as requested.
  • Scales to multi-language repos and large codebases with minimal setup.
  • Use Case: On a new project, automatically generate a unified README and API surface from source files.

Quick Start

Ask doc-gen to process a target file or directory to generate documentation in the repository's preferred style.

Frequently Asked Questions about doc-gen

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

FAQPage Schema
How do I auto-generate project documentation from code?

To auto-generate project documentation, you can use a tool that analyzes your code structure and project conventions to produce accurate, style-consistent docs. It inspects the codebase to ensure the output aligns with existing repository styles.

Can I generate module-level READMEs and API references across multiple languages?

Yes, you can generate module-level READMEs and API references across multiple languages. The process scales to multi-language repos and large codebases by adapting to the target directory's structure and conventions with minimal setup.

How do I ensure my auto-generated docs match existing repository conventions?

Auto-generated docs match existing repository conventions by detecting the project's code structure and style during analysis. This mechanism ensures the output produces non-boilerplate, accurate descriptions that align with your current documentation format.

Does automated code documentation work for function-level descriptions in large codebases?

Yes, automated code documentation works for function-level descriptions in large codebases. It scales to process target files or directories, generating detailed function docs, module READMEs, and API surfaces while maintaining style consistency.

What is the best way to generate an API surface from source files?

The best way to generate an API surface from source files is to analyze the code structure and project style automatically. This approach inspects the repository to produce unified, non-boilerplate API references that match your conventions.

When should I not use automated documentation generation for my codebase?

You should not use automated documentation generation when your project lacks existing code structure or conventions to analyze, as the tool relies on inspecting repository style to produce accurate, non-boilerplate descriptions and ensure style consistency.