Agent skill · luongnv89
doc-manager
Generate or update docs to match the code, citing each claim to path:line and asking on ambiguity; runbook docs also get a check-only validation script. Don't use for API-reference autogen (JSDoc/Sphinx), landing pages, or CLAUDE.md/AGENTS.md.
What it needs
About 7k tokens when loaded.
What this skill does
Doc Manager Keep a project's Markdown documentation true to the code. Every run ends with each doc updated, verified-current, or flagged — and every non-obvious claim traced to a source. Scope is Markdown only (README.md, docs/.md, per-component READMEs); docstrings and comments are read as source-of-truth but not rewritten. Prime directive — never invent. If the code does not show it and the user has not stated it, do not write it. When a fact is unclear or docs conflict with code, ask the user, then record the resolution in docs/DECISIONS.md. A guess is a defect here, not a convenience. Repo Sync Before Edits (mandatory) Before creating/updating/deleting any file in the repo, sync the current branch: If the tree is dirty: git stash push -u -m "pre-sync" → sync → git stash pop. If origin is missing, or rebase/stash conflicts occur, stop and ask before continuing. Prerequisites Validate before starting; if any fails, stop and surface it: Git: git --version ≥ 2.30. Working tree clean or stashable. Remote: git remote get-url origin resolves (needed for sync). If absent, ask before any pull/rebase. Write access: analysis needs read only. Writing files needs the tree to be writable; if read-only, emit a diff/summary instead of writing. Mermaid (optional): only if diagrams must be exported — command -v mmdc. Branch selector Work one doc at a time. For each doc in the inventory, pick the path: Situation Path --- --- A needed doc does not exist A. Generate A doc exists but may not match the code B. Reconcile A doc or a section of one covers deploy / release / setup / operational process also run C. Runbook add-on A single run usually mixes A and B across the inventory. C is additive — it layers onto whichever of A/B produced runbook content. Classify at the section level: a doc that mixes a runbook section with reference content gets C applied to the runbook section only, not the whole file. Workflow 0. Feature branch 1. If already on a task feature branch, skip. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills luongnv89/doc-manager