vibe-documentlisted

Generates complete documentation for vibe-* projects — inline code docs, README.md, CHANGELOG.md, API reference, and component library docs. Scans all source files and documents everything in one session. Triggers on "document:" prefix, "write docs for", "generate documentation", "add JSDoc", "add docstrings", "document this feature", "we need a README", "generate a changelog", "document the API", "document the components", "missing docs", "no documentation". Runs automatically after vibe-init on undocumented legacy projects, after vibe-add-feature to document what was built, and when vibe-review flags missing documentation as P1 or P2. Always use when documentation is absent, incomplete, or out of date. Shows full doc plan first — writes everything on explicit approval.
aakashdhar/vibe-skill · ★ 7 · Data & Documents · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe Document Skill Generates complete, accurate documentation grounded in actual code. Inline docs in source files. Standalone markdown docs at project root. Everything documented in one session. No gaps left for later. **Runs in agent mode (Claude Code / Cursor). Requires filesystem access.** --- ## The principle this enforces Documentation written after the fact from memory is inaccurate. Documentation generated from the actual code is honest. This skill reads the source first, documents what it finds — not what someone thinks is there. --- ## Entry points ### Entry point A — On demand Triggered by: `document:`, "write docs for X", "generate documentation", "missing docs" Default scope: scan all source files, document everything in one session. If the user specifies a narrower scope ("document the API" / "document the auth module") — scope to that area only. Confirm scope before proceeding. Go to **Step 0**. ### Entry point B — After vibe-init Triggered automatically at the end of a `vibe-init` session on a legacy project. The codebase has just been scanned — CODEBASE.md is fresh and accurate. No additional scanning needed for Step 1. Scope: full project — everything. Go to **Step 0** → skip the scan in Step 1, read directly from CODEBASE.md. ### Entry point C — After vibe-add-feature Triggered automatically at the end of a `feature:` session. Scope: files listed in `FEATURE_TASKS.md` under **Touches** + any new files created. README.md is always updated r