lmiranda
2d51df7a42
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
name, description
| name | description |
|---|---|
| test setup | Detect test framework, configure test runner, and initialize test structure |
/test setup
Setup wizard for test automation. Detects existing frameworks or helps choose one.
Visual Output
+----------------------------------------------------------------------+
| TEST-PILOT - Setup |
+----------------------------------------------------------------------+
Skills to Load
- skills/framework-detection.md
Process
-
Project Detection
- Scan for existing test directories (
tests/,test/,__tests__/,spec/) - Detect language from file extensions and config files
- Identify existing test framework configuration
- Scan for existing test directories (
-
Framework Detection
- Python: check for pytest.ini, setup.cfg [tool.pytest], pyproject.toml [tool.pytest], conftest.py, unittest patterns
- JavaScript/TypeScript: check for jest.config.js/ts, vitest.config.ts, .mocharc.yml, karma.conf.js
- E2E: check for playwright.config.ts, cypress.config.js, selenium configs
-
Configuration Review
- Show detected framework and version
- Show test directory structure
- Show coverage configuration if present
- Show CI/CD test integration if found
-
Recommendations
- If no framework detected: recommend based on language and project type
- If framework found but no coverage: suggest coverage setup
- If no test directory structure: propose standard layout
- If missing conftest/setup files: offer to create them
Output Format
## Test Environment
### Detected Framework
- Language: Python 3.x
- Framework: pytest 8.x
- Config: pyproject.toml [tool.pytest.ini_options]
### Test Structure
tests/
conftest.py
unit/
integration/
### Coverage
- Tool: pytest-cov
- Current: 72% line coverage
### Recommendations
- [ ] Add conftest.py fixtures for database connection
- [ ] Configure pytest-xdist for parallel execution
- [ ] Add coverage threshold to CI pipeline