docs
Dispatch docs subagent to audit, generate, and validate documentation against the codebase.
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 automagik-dev-genie-docs
Repository
Skill path: skills/docs
Dispatch docs subagent to audit, generate, and validate documentation against the codebase.
Open repositoryBest for
Primary workflow: Write Technical Docs.
Technical facets: Full Stack, Tech Writer.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: automagik-dev.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install docs into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/automagik-dev/genie before adding docs to shared team environments
- Use docs for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: docs description: "Dispatch docs subagent to audit, generate, and validate documentation against the codebase." --- # /docs — Documentation Generation Audit existing documentation, identify gaps, generate what's missing, and validate every claim against actual code. Can be invoked standalone or as part of `/work`. ## When to Use - Codebase has undocumented modules, APIs, or workflows - Existing documentation is stale or references removed features - A wish deliverable includes documentation - After significant code changes that invalidate existing docs - After `/work` completes — suggest `/docs` to document what changed ## Documentation Surfaces Audit and maintain these doc types: | Type | Location | Purpose | |------|----------|---------| | **README** | `README.md`, `*/README.md` | Project/module overview, setup, usage | | **CLAUDE.md** | `CLAUDE.md`, `*/CLAUDE.md` | Project conventions, commands, gotchas for AI agents | | **API docs** | `docs/api/`, inline JSDoc/TSDoc | Endpoint contracts, request/response schemas | | **Architecture** | `docs/architecture.md`, `ARCHITECTURE.md` | System design, data flow, component relationships | | **Inline docs** | JSDoc, TSDoc, docstrings | Function/class/module-level documentation | **CLAUDE.md is a first-class documentation surface.** When the codebase changes significantly (new commands, changed conventions, removed features), flag CLAUDE.md for update. CLAUDE.md should always reflect the current state of the project. ## Flow 1. **Audit existing docs:** scan all documentation surfaces above — map what exists. 2. **Identify gaps:** compare documentation against actual code — find what's missing, outdated, or wrong. Pay special attention to CLAUDE.md accuracy. 3. **Generate:** write documentation to fill the gaps, matching project conventions. 4. **Validate against code:** verify every claim — file paths exist, APIs match, behaviors are accurate. 5. **Report:** return list of created/updated files with validation results. ## Dispatch ```bash # Spawn a docs subagent genie spawn docs ``` ## Rules - Validate every claim against actual code — no fiction. - No dead references — every path, function, and API mentioned must exist in the codebase. - Match existing project conventions for documentation style and structure. - Never document features that don't exist yet. - Include validation evidence in the report — not just "docs written" but "docs written and verified."