Build Docs
| This documentation was generated with the assistance of AI. Please report any inaccuracies. |
Build a repository’s existing Antora documentation site as-is, scaffolding it first via iru-setup-antora if it
doesn’t exist yet. This skill never edits page content, nav.adoc, or antora.yml beyond what bootstrapping
requires — it only ensures the toolchain/module exist and runs the build.
Purpose
iru-build-docs answers a narrower question than iru-update-docs: "does the docs site build right now?" rather than
"does the docs site reflect recent code changes?". It does no code exploration and makes no content edits to
any existing page — it locates the Antora module, confirms Node.js and the playbook are usable, installs
dependencies, and runs the build, reporting the built index.html path or the exact build error. Reach for it
to check the site compiles or to get the built HTML output, not to bring stale content up to date.
Outputs
-
The static site built at the docs module’s build output directory (e.g.
docs/build/site), with the path to itsindex.htmlreported back. -
If no Antora module existed anywhere in the repository and the user agreed to bootstrap one: a newly scaffolded Antora module (via
iru-setup-antora), then the build proceeds against it. -
No
.adocpage content,nav.adoc, orantora.ymlis ever edited by this skill itself (onlyiru-setup-antora, when delegated to, may write those as part of scaffolding). -
A report stating whether the module already existed or was just set up, whether the build succeeded or failed, and the path to the built
index.htmlor the build error — nothing else.
Execution flow
Dependencies
Invokes
-
Setup Antora — Step 1, conditionally: only when no
antora.ymlis found anywhere in the repository, and only after asking the user whether to bootstrap Antora documentation now.
Source
SKILL.md on GitHub — the file this page was generated from.