use-branch-complete
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Phase 5 of disciplined development. Validates system against original requirements through system testing and user acceptance testing (UAT). Uses structured stakeholder interviews to gather sign-off and traces defects back to research or design phases.
Web API 測試實作技能,協助開發者使用 Testcontainers + Reqnroll 撰寫完整的 API 整合測試,包含 Docker 測試環境、BDD 情境定義與測試步驟實作。
Use to avoid critical testing mistakes. Five Iron Laws: Never test mock behavior, Never add test-only methods, Never mock without understanding, Always integration test, Always test error paths.
A complete skill with all fields present for testing
Write or update unit (not integration) tests in this repo, use Verify snapshot testing for source generator output, and run/accept snapshots via the provided scripts.
Automate visual validation of component states to catch styling regressions.
Claude writes fast, reliable tests using Vitest for TypeScript/JavaScript projects. Use when writing unit tests, component tests, setting up mocks, snapshot testing, or configuring test coverage.
Use when creating or editing slash commands - applies TDD to slash command documentation by testing with SlashCommand tool and subagents before deployment, preventing inverted logic and untested conditionals
Create Behavior-Driven Development (BDD) feature files using Gherkin syntax. Write clear, executable specifications that describe system behavior from the user's perspective. Use for requirements documentation, acceptance criteria, and living documentation.
Executes tests, analyzes test results, checks test coverage, and provides comprehensive testing status overview. Primarily for Go projects. Activates after implementing/modifying code to verify correctness, or when explicitly requested to assess test suite health.
Fast, repeatable UI verification using Puppeteer without paying browser startup per test. Use scenario suites + deterministic fixtures before jumping to full Jest E2E.
Generates comprehensive tests for Ishkul code including state transition tests that catch React Rules of Hooks violations. Creates tests for frontend screens/components (Jest + RTL) and backend handlers (Go testing + testify). Use when creating new code or adding test coverage.
TypeScript testing conventions and TDD practices. Use when writing tests, fixing bugs, or organizing test files.
Applies current Go testing best practices. Use when writing or modifying Go test files or advising on Go testing strategies.
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
Write production-grade React tests with Testing Library, MSW, and comprehensive coverage patterns
Test Spring Boot applications - MockMvc, TestContainers, test slices, integration testing
Run tests from skill examples and generate a report (project)
Use when testing Fusionaly features, checking for regressions, or verifying releases - supports OSS and Pro, install scripts, E2E tests, and feature testing