From testbench
Generates tests for a source file or function, matching project conventions by reading existing test files for import style, mocks, assertions, naming. Supports E2E; one file at a time.
How this skill is triggered — by the user, by Claude, or both
Slash command
/testbench:generateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a test file for a given source file. The generated test matches the project's existing conventions -- import style, mock patterns, assertion style, file placement, and naming.
Generate a test file for a given source file. The generated test matches the project's existing conventions -- import style, mock patterns, assertion style, file placement, and naming.
Load each step through the fetch command (handles caching, decryption, and auth):
"~/.composure/bin/composure-fetch.mjs" skill testbench generate {step-filename}
Do NOT read cache files directly — they are encrypted at rest. Always use the fetch command above.
| # | File |
|---|---|
| 1 | 01-load-config.md |
| 2 | 02-analyze-source.md |
| 3 | 03-read-existing-tests.md |
| 4 | 04-generate-test.md |
| 5 | 05-run-and-fix.md |
npx claudepluginhub hrconsultnj/claude-plugins --plugin testbenchGenerates tests for any file type with automatic framework detection, project convention matching, and type-specific routing (React, Vue, Python, Go, Rust, PHP, E2E).
Generates unit tests matching project patterns and frameworks like Jest/Vitest (JS/TS), pytest (Python), Go testing, JUnit (Java), RSpec (Ruby).