docs

Invoke the readme mode with an optional path, and the Skill reads package.json, entry points, and directory structure to write a README with quick start, configuration, and project structure sections. All commands are validated against actual package.json scripts before output.

Use update mode on the existing doc file. It extracts every factual claim, verifies endpoints and schemas against route and controller source files, patches stale sections, and marks unverifiable claims with TODO comments instead of rewriting from scratch.

Yes, changelog mode uses git-cliff when available, or falls back to parsing git log with conventional commit prefixes (feat, fix, refactor, docs, chore). It supports full history or a specific tag range like v1.2.0..v1.3.0 and enriches cryptic messages by reading diffs.

Yes, the Skill detects the project's tooling from lockfiles and manifests such as pnpm-lock.yaml, pyproject.toml, go.mod, and Cargo.toml. Documented install, dev, test, and build commands always match the detected stack rather than defaulting to npm.

Architecture diagrams and user-facing product docs are out of scope. Claims whose source files cannot be found are marked as unverifiable rather than guessed, and if more than half of an existing doc is stale, a full rewrite is recommended instead of patching.