run-module-tests
Runs tests for Spring Boot modules with proper Java version handling. Use when testing code changes, debugging test failures, or verifying module functionality.
Discover tools testing skills, compare source repositories and read the instructions for each workflow.
Runs tests for Spring Boot modules with proper Java version handling. Use when testing code changes, debugging test failures, or verifying module functionality.
Develop, test, and maintain the Paracle framework codebase. Use when implementing features, fixing bugs, writing tests, or refactoring framework code.
Develop, test, and maintain the Paracle framework codebase. Use when implementing features, fixing bugs, writing tests, or refactoring framework code.
Develop, test, and maintain the Paracle framework codebase. Use when implementing features, fixing bugs, writing tests, or refactoring framework code.
Write comprehensive tests (unit, integration, e2e), manage test coverage, and ensure code quality. Use when writing tests, improving coverage, or debugging test failures.
Write comprehensive tests (unit, integration, e2e), manage test coverage, and ensure code quality. Use when writing tests, improving coverage, or debugging test failures.
Complete guide to using Playwright MCP server with Claude Code
Integration testing patterns, strategies for testing component interactions, and managing test dependencies
RED-GREEN-REFACTOR cycle for writing bulletproof code with strong test coverage
Unit testing best practices, patterns, and strategies for comprehensive test coverage
Write RSpec tests for Co-Create Rails app following project conventions. Use when writing model tests, request tests, or testing features like authentication, authorization, validations, associations, scopes, c...
Test all components of the project. Use after each edit to ensure code changes do not regress.
Skill for hunting flaky tests and race conditions by running specific tests multiple times.
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on ne...
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
Guide for writing Go tests following this project's patterns including httptest, test organization, and coverage requirements.
[60] VALIDATE. Ensure new (staged and unstaged) changes are covered by tests at >70% and the full test suite is green. Use when asked to validate coverage for recent changes, add tests for modified code, or ver...
Audits UI code for accessibility, performance, and UX compliance. Use when reviewing components, checking accessibility, or validating UI before shipping.
Property-based testing with clojure.test.check. Use when writing generative tests, creating custom generators, or debugging shrinking behavior. Triggers on test.check imports, prop/for-all, gen/* usage, or ques...
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without unders...
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure fir...
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check...
Test-Driven Development workflow guide. TODO - This skill is a placeholder for future development. Will cover TDD patterns for Rust, TypeScript, and Tauri apps.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.