Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/setup-ai:testThe summary Claude sees in its command listing — used to decide when to auto-load this command
Add tests for: **$ARGUMENTS** (if empty, cover my most recent changes). Use the `write-tests` skill (or the `test-engineer` subagent). Detect the project's test runner and style, write tests for the happy path plus edge/error cases, then **run the suite** and report the result verbatim. Don't weaken assertions to pass — if a test exposes a real bug, report it.
Add tests for: $ARGUMENTS (if empty, cover my most recent changes).
Use the write-tests skill (or the test-engineer subagent). Detect the project's test runner and
style, write tests for the happy path plus edge/error cases, then run the suite and report the
result verbatim. Don't weaken assertions to pass — if a test exposes a real bug, report it.
npx claudepluginhub linder3hs/setup-ai --plugin setup-ai/testRuns a TDD workflow: write failing tests, implement code, and verify. For bug fixes, uses the Prove-It pattern to reproduce, fix, and confirm.
/testRuns pytest tests for CLI harness on local path or GitHub repo, verifies CLI resolution, and updates TEST.md with results if all pass.
/testExecutes unit, integration, or e2e tests with coverage analysis, quality metrics, failure diagnostics, and optional watch mode or auto-fixes.
/testGenerates test strategy overview, unit and integration test code, coverage analysis, execution plan, and maintenance roadmap for a specified component or feature.
/testLaunches Chrome for manual UI testing at given URL, monitors console errors during interaction, generates report with screenshots and logs on completion.
/testInvokes the testing-coach agent to provide guidance on screen reader, keyboard navigation, and automated testing for the given request.