Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From project-starter
Adds tests for recently changed files or a specified target. Detects the project's test framework, analyzes code, and writes tests covering happy path, edge cases, and error handling.
How this command is triggered — by the user, by Claude, or both
Slash command
/project-starter:add-tests file path or function nameThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
## Context - Recently modified files: !`git diff --name-only HEAD~3 2>/dev/null | grep -E '\.(ts|tsx|js|jsx|py|go|rs)$' | head -10 || echo "No recent changes"` - Test framework detection: !`cat package.json 2>/dev/null | grep -E '"(jest|vitest|mocha)"' | head -1 || ls pytest.ini pyproject.toml 2>/dev/null | head -1 || echo "Unknown test framework"` - Existing test files: !`find . -name "*test*" -o -name "*spec*" 2>/dev/null | grep -E '\.(ts|tsx|js|jsx|py|go)$' | head -10 || echo "No test files found"` - Test directory structure: !`ls -la tests/ test/ __tests__/ spec/ 2>/dev/null | head -20...
git diff --name-only HEAD~3 2>/dev/null | grep -E '\.(ts|tsx|js|jsx|py|go|rs)$' | head -10 || echo "No recent changes"cat package.json 2>/dev/null | grep -E '"(jest|vitest|mocha)"' | head -1 || ls pytest.ini pyproject.toml 2>/dev/null | head -1 || echo "Unknown test framework"find . -name "*test*" -o -name "*spec*" 2>/dev/null | grep -E '\.(ts|tsx|js|jsx|py|go)$' | head -10 || echo "No test files found"ls -la tests/ test/ __tests__/ spec/ 2>/dev/null | head -20 || echo "No standard test directory"Add tests for the specified target:
Target: $ARGUMENTS
If no target specified, focus on recently modified files that lack test coverage.
npx claudepluginhub dientm/claude-workflow-v212plugins reuse this command
First indexed Jan 2, 2026
Showing the 6 earliest of 12 plugins
/add-testsAdds tests for recently changed files or a specified target. Detects the project's test framework, analyzes code, and writes tests covering happy path, edge cases, and error handling.
/test-tddScans modified source files, locates their corresponding test suites, and runs them with the appropriate test runner.
/write-testsGenerates thorough unit tests for a specified file or function, auto-detecting the test framework and following project conventions. Runs tests after writing to confirm they pass.
/write-testsWrite unit tests for source files, matching the target repo's observed test conventions
/generate-testsGenerates comprehensive unit tests for source code files, covering happy paths, edge cases, error handling, mocking, and assertions. Auto-detects test framework (Jest, pytest, JUnit, etc.) and produces structured test files.
/add-testsGenerates unit and E2E tests for a completed phase by analyzing implementation files against UAT criteria, presenting a test plan for approval, and committing RED-GREEN tests.