write-tests
Generate comprehensive test coverage for existing code.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/nimbalyst/nimbalyst/HEAD/.claude/commands/write-tests.md -o ~/.claude/commands/write-tests.mdwrite-tests.md
# /write-tests Command Generate comprehensive test coverage for existing code. ## What This Command Does 1. Analyzes code to test 2. Identifies test cases (happy path, edge cases, errors) 3. Generates test code in appropriate framework 4. Includes setup/teardown as needed ## Usage `/write-tests [file or function]` ## Test Generation Approach - Uses existing test framework in project - Follows project test patterns - Includes meaningful test names - Covers edge cases and error conditions - Adds necessary mocks/fixtures ## Best Practices - Review generated tests for accuracy - Adjust assertions as needed - Run tests to verify they pass - Add tests incrementally for large files
Run E2E tests in a dev container for isolated, reproducible test execution. Use proactively when asked to run Playwright tests, E2E tests, or when in a worktree. Handles the full Docker container lifecycle automatically.
Prepare and execute an Android release (patch/minor/major)
Gather details and draft an actionable bug report for developers.
Create a git commit with concise, bullet-point commit message
Create a new plan document for tracking work.
Run E2E tests in a dev container (isolated environment)
Execute a plan document while keeping progress synchronized.
Investigate a Nimbalyst performance problem (freeze, lag, idle CPU, slow op, memory growth) with measured evidence before proposing a fix.