← ClaudeAtlas

repo-docs-discoverylisted

Upstream-resolution playbook for turning an installed package into an explicit pinned docs source before calling llm-docs generate. Use to resolve a package to its repo, tag, commit, and docs tree, especially across monorepos where a package's docs live under another package's tree.
Zyepher/llm-docs-generator · ★ 5 · AI & Automation · score 75
Install: claude install-skill Zyepher/llm-docs-generator
# repo-docs-discovery This skill resolves the question Step 1 of the `llm-docs-generator` playbook asks: *for the exact version this project runs, where is the authoritative docs tree, at which commit?* You investigate and decide; `llm-docs` only converts the explicit local path you hand it. Hand generation a concrete answer: **repo URL + tag + commit + docs subtree path**, plus notes on anything non-obvious (drafts, framework subtrees, docs that live in another package's repo). Every step states WHY so you can adapt it to a repo whose layout differs from the examples. ## Division Of Labor (never violate) - You own version choice, source authority, docs-tree selection, and task fit. - The CLI owns bounded inspection, parsing, formatting, and honest failure. It never decides which repo, tag, or docs path is authoritative. - Never pass a package name, repo URL, docs URL, or discovery report to `generate --source`. Resolve it to an explicit local path first. - Run `llm-docs capabilities --json` before assuming a discovery mode exists; modes not reported there are unavailable unless the installed CLI says otherwise. `llm-docs agent doctor --json` is read-only diagnostics; do not claim `agent install codex` or other lifecycle commands unless capabilities reports them. - Never store credentials or tokens in reports, manifests, or notes. - Do not execute repository scripts, docs-build scripts, or install hooks from an inspected source. ## Step 1 — Package → Repo (primary eviden