Build a verified Markdown documentation tree from the repository itself, review it, and then publish it through the same safe DocsPress workflow.
1. Add the DocsPress skills
Run this in the repository before asking your coding agent to create the documentation:
npx skills add Automattic/docspress --all --full-depth2. Create the docs
Use $generate-docs-from-source to inspect this repository and create verified DocsPress-compatible documentation from its source code and tests. Preserve useful existing docs, show me the proposed docs tree, and do not publish anything yet.
$generate-docs-from-source
@repository
src/
test/
docs/
If the repository already has a usable Markdown tree, skip generation and publish the existing docs.
What this path does
The generation workflow asks a repository-aware coding agent to:
- Inventory public APIs, commands, configuration, tests, examples, and existing documentation.
- Build a coverage map that ties every documentation claim to repository evidence.
- Create or improve a navigable
docs/hierarchy. - Use DocsPress Gutenberg blocks only when their semantics improve the page.
- Validate routes, links, examples, block attributes, and documented behavior.
- Hand the reviewed tree to
$docspress-installfor a manual draft dry run.
Continue
Neutral
Start with evidence, not a template
The agent derives the documentation structure from the project’s real public surface and tests before writing pages.