feat(commands): make dispatch files active command handlers

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>
This commit is contained in:
2026-02-08 19:12:12 -05:00
parent bbce9ed321
commit 271e0210a5
25 changed files with 324 additions and 89 deletions

View File

@@ -1,18 +1,27 @@
---
description: Test automation — generate tests, analyze coverage, manage fixtures
name: test
description: Test automation — type /test <action> for commands
---
# /test
Test automation toolkit for unit, integration, and end-to-end testing.
## Sub-commands
When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description |
|-------------|-------------|
## 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