manni

Almost every command reads manni <domain> <subcommand> [<subcommand>] [<arguments>], and the domain is the tool. The two exceptions run across the tools, and the next section covers them. manni meta validate docs/ runs the metadata tool’s validate against docs/, and manni meta schemas vendor reaches a verb one level down. Each tool has its own commands, its own section of this site, and its own key in one shared config file, manni.config.yaml. Install the package once and every tool is there.

npm install -D @hawkeyexl/manni
npx @hawkeyexl/manni meta validate docs/
npx @hawkeyexl/manni docevals run docs/ --deterministic-only

Everything a repository set up, in one command

manni status says which tools a repository set up. manni check runs every check they carry, and skips the rest. It is the same command in CI, by hand, and in an agent session. There, the manni plugin for Claude Code runs it after each edit.

npx @hawkeyexl/manni status
npx @hawkeyexl/manni check

manni checkGate everything a repository set up with one command, locally and in CI. Tools nobody set up are listed as skipped and never block.

Claude Code pluginInstall the manni plugin, and an agent gets each error at the edit that caused it and can't finish with one outstanding.

The tools

metaValidate the presence and format of document metadata against JSON Schema, built for CI. Read, query and fill it too. Formerly published as docmeta.

a11yCrawl a site and check every page for accessibility violations with axe-core, built for CI.

citePin a sentence to the source lines it rests on, and find out when those lines move or change. From git alone, no model, no network.

lintCheck that every page has the shape its doctype promises: the sections a how-to needs, in order, with the steps and code blocks inside them.

docevalsDeterministic and LLM-as-judge evals for documentation pages, driven by frontmatter. Code first, an AI judge second, a human last.

tracevalsAdherence evals for AI agent session traces. You wrote the instructions; point it at a session that already happened and find out whether the agent followed them.

graphDerive a knowledge graph from documentation frontmatter and formatting, check it against SHACL shapes, and publish it for retrieval. Deterministic, with no model in the loop.

siteStart, build and preview the docs site with one command per job, whatever framework it runs on, on the port the collection url names.

keySet and rotate the family encryption key, so a required field or a private source path is on the page without being readable there.

termDefine a docset's terms, check every concepts: reference against them, generate a Vale style from them, and move the set between glossary formats, TBX and CSV.

strategyKeep the audiences, personas and journeys a docset serves as records, and check that every page naming one names a record that exists.

testRun the Doc Detective tests embedded in the docs, and gate on them with the same exit codes and annotations as every other manni check.

meta checks what a page says about itself. lint checks whether it is shaped like what it says it is. cite checks that what a page says about the code is still true. docevals checks that a page still meets the quality bar its team wrote down. tracevals checks that an agent session followed the instructions it ran on. term checks that the terms a page names are defined, and carries those terms into Vale and translation. strategy checks that the audiences, personas and journeys a page names are ones the docset keeps records of. graph checks what the pages say about each other, which is the only question no single file can answer. key sets and rotates the one encryption key that meta and cite encrypt values with. test checks that a procedure still works when someone follows it. site runs the docs site itself, the one a11y crawls, through its framework’s own commands. manni --help lists exactly the tools the package carries.

cite, docevals, tracevals, key, site, term, strategy, lint, graph and test are in beta. Their commands, config keys and output can change in any release, without notice.

Coming from docmeta?

The metadata tool used to be the whole package. Three things changed, and nothing else did:

• The command. docmeta validate … is now manni meta validate …. The package still installs a docmeta bin that runs the same program, so existing scripts keep working while you move them.
• The config file. manni.config.yaml, with the metadata tool’s keys under meta:. A docmeta.config.yaml is still read, with a warning. See the configuration reference.
• The GitHub Action. uses: hawkeyexl/manni@v4 now runs manni check, every check the repository has set up. Add command: meta validate to run the metadata check alone, with the inputs it took before. See the Action reference.

Every built-in schema keeps its old published URL as well as its new one, so a $schema line written before the rename still resolves offline. See the built-in schema registry.