/test-suite-author¶
Testing class
Writes test source into the repo and executes it — the only class that does both. Shared rules: CONVENTIONS-testing.md.
Umbrella over /test-plan → /test-author → /test-data: plans the cases, generates specs in the repo's own framework, and adds fixtures. PAUSES after every stage for review by default; --yes runs unattended for a workflow. Writes only inside detected test directories and PROPOSES the commit — never runs git.
At a glance¶
| Run it | /test-suite-author |
| Class | testing |
| Version | 0.1.0 |
| Author | navjyotnishant |
| Cost | three stages, roughly one agent call each — cost scales with the number of cases, not the size of the repo |
| Needs | /test-plan · /test-author · /test-data · a detected test framework · a connected tracker (MCP) |
| Source | skills/test-suite-author/SKILL.md |
What it needs, and what happens without it¶
Every tool is detected at runtime — none is installed for you.
| Tool | Without it |
|---|---|
/test-plan |
BLOCK — nothing to generate from |
/test-author |
plan only; report that specs were not written |
/test-data |
specs only; say fixtures were skipped |
| a detected test framework | SKIP at the author stage — never pick one |
| a connected tracker (MCP) | paste-in fallback (§A5) |
Agents it spawns¶
This skill spawns no subagents — it runs inline.
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.