novahiz-docslisted

novahiz-docs manages the project documentation lifecycle: init creates the structure, update keeps it current, check reports drift. Use to set up project documentation or keep existing docs in sync with the codebase. Triggers on: "init docs", "documentation structure", "sync docs", "docs drift", "project documentation".
novahiz/novahiz · ★ 1 · AI & Automation · score 73

Install: claude install-skill novahiz/novahiz

# novahiz-docs Documentation for a project that evolves with its code. Three commands drive the lifecycle: init, update, check through converge. ## Commands ### init Creates `novahiz-docs/` with four files: ``` novahiz-docs/ ARCHITECTURE.md system shape, components, data flow CONVENTIONS.md naming, style, patterns in force DECISIONS.md ADR log STANDARDS.md quality, testing, security bar ``` Process: 1. Scan manifests, tree, configs, and any existing docs. 2. Detect stack, patterns, and conventions already in the code. 3. Fill each template with observed facts only. 4. Show the result for confirmation before writing. Detection sources: | File | Where the facts come from | |---|---| | ARCHITECTURE.md | directory layout, entry points, imports, configs | | CONVENTIONS.md | code patterns, lint config, naming styles | | DECISIONS.md | empty at creation, grows as decisions land | | STANDARDS.md | test framework, CI config, security tools present | ### update Runs a manual refresh against the current project state. 1. Read what the docs say today. 2. Scan the project as it stands. 3. Diff the two: changed, new, stale. 4. Propose the edits through the `question` tool. 5. Apply only what the user accepts. ### Drift check through converge When `novahiz-converge` runs and `novahiz-docs/` exists, it looks for architectural drift (new modules, dependencies, patterns), flags stale sections, and adds proposals to the convergence report. Nothing is wri