Documentation
Agent instructions
Give your agent the instructions bundled with its installed version.
The guides on this website explain Supercov to people using coding agents. For an agent doing the work, use the instructions bundled with its installed CLI. Those match the commands and behavior of that version.
Give your agent the right starting point
You can add this to a task or your project’s agent instructions:
Use npx supercov for coverage. Before starting, read its bundled docs:
`npx supercov docs agent-loop` for the testing workflow and
`npx supercov docs assertion-agent` for assertion mapping.
Follow those instructions using this project's actual test command.These instructions tell the agent how to inspect gaps, keep comparisons on the same suite, build and validate assertion maps, and stop when a result cannot be established. They don’t start another agent or run tests by themselves.
Read the installed instructions
npx supercov docs
npx supercov docs agent-loop
npx supercov docs assertion-agent
npx supercov docs cli
docs lists the available topics. Add a topic to print its Markdown guide
in the terminal. It doesn’t fetch this website, start an agent or measure
coverage. Humans can read these guides too; they include the details an agent
needs when carrying out a task.
The website groups information for browsing, so page names don’t always match CLI topics:
| Website guide | Installed guide |
|---|---|
| Installation | npx supercov docs getting-started |
| Lines and branches, MC/DC | npx supercov docs coverage-model |
| Assertion coverage | npx supercov docs assertions |
| Map with an agent | npx supercov docs assertion-agent |
| Assertion evidence | npx supercov docs assertion-evidence |
| Reading the results | npx supercov docs verification |
For a command’s flags and arguments, use --help, such as
npx supercov runs latest --help.
Detailed guides on the website
- CLI reference: commands, flags and queries.
- Runner support: supported environments and measurement limits.
- Map with an agent: the assertion mapping and review workflow.
- Assertion map format: fields, references and validation.
- Assertion evidence: why a statement is or isn’t credited.
- Runs and evidence: recorded runs, comparisons and storage.
The full testing workflow and assertion mapping instructions are also available as plain Markdown, without the website navigation.
For tools that fetch documentation over HTTP, llms.txt indexes the guides and the version-pinned Markdown reference. Prefer the installed instructions when the agent’s CLI version differs from the website’s version.