/test-report¶
Testing class
Writes test source into the repo and executes it — the only class that does both. Shared rules: CONVENTIONS-testing.md.
Use this skill when the user asks \"are we ready to release\", \"show test coverage against the requirements\", \"write the test report\", or wants a traceability matrix linking requirement to case to run status to defect. Reads the run manifest and the flake ledger, and reports what is covered, what is not, and what open risk a release carries. States coverage gaps rather than implying completeness. Advises only: it writes no test and makes no release decision. --html renders the same model as a self-contained page with per-spec trend sparklines from the flake ledger.
At a glance¶
| Run it | /test-report |
| Class | testing |
| Version | 0.1.0 |
| Author | navjyotnishant |
| Needs | the run manifest (§T13) · /test-plan cases · the flake ledger (§T14) · docs-designer (this toolkit) · a connected tracker (MCP) |
| Source | skills/test-report/SKILL.md |
What it needs, and what happens without it¶
Every tool is detected at runtime — none is installed for you.
| Tool | Without it |
|---|---|
the run manifest (§T13) |
BLOCK — a report with no run behind it is fiction |
/test-plan cases |
report spec → result only, and say the requirement link is missing |
the flake ledger (§T14) |
report without confidence weighting, and say so |
docs-designer (this toolkit) |
markdown only; say the page was not rendered |
| a connected tracker (MCP) | list defects inline; paste-ready (§A5) |
Agents it spawns¶
docs-designer— Turn a structured doc model into a browsable documentation surface. By default it emits a GENERATED…
The procedure¶
The executable steps live in the skill file itself and are deliberately not reproduced here: they are instructions to the model at runtime, not documentation.