lmiranda
271e0210a5
All 25 dispatch files now have name: in frontmatter with Workflow section that displays sub-commands and prompts for selection. Bare /noun invocation is now useful instead of a dead end. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
28 lines
844 B
Markdown
28 lines
844 B
Markdown
---
|
|
name: test
|
|
description: Test automation — type /test <action> for commands
|
|
---
|
|
|
|
# /test
|
|
|
|
Test automation toolkit for unit, integration, and end-to-end testing.
|
|
|
|
When invoked without a sub-command, display available actions and ask which to run.
|
|
|
|
## Available Commands
|
|
|
|
| Command | Description |
|
|
|---------|-------------|
|
|
| `/test setup` | Setup wizard — detect framework, configure test runner |
|
|
| `/test generate` | Generate test cases for functions, classes, or modules |
|
|
| `/test coverage` | Analyze coverage and identify untested paths |
|
|
| `/test fixtures` | Generate or manage test fixtures and mocks |
|
|
| `/test e2e` | Generate end-to-end test scenarios |
|
|
| `/test run` | Run tests with formatted output |
|
|
|
|
## Workflow
|
|
|
|
1. Display the table above
|
|
2. Ask: "Which command would you like to run?"
|
|
3. Route to the selected sub-command
|