Discover data ai testing skills, compare source repositories and read the instructions for each workflow.
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automa...
Execute a single user story from prd.json. Use during Ralf loop iterations to implement stories correctly.
Use when strict test-first discipline is explicitly requested or required for a change.
Run Go tests with race detection and coverage. Use when asked to run tests, check test coverage, or verify Go code functionality.
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.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage.
Control a Playwright browser via CLI - navigate, interact, and screenshot
テスト駆動開発(TDD)の進め方をガイドし、テスト設計/実装/リファクタリングの反復を支援する。ユーザーが「TDDで実装して」「テストファーストで進めたい」「レッド・グリーン・リファクタで」「テストを先に書いて」などと依...
Interactive skill testing and ground truth generation. Use when testing a skill's code generation capabilities by executing generated code and saving verified working examples. Invoke with: /skill-test
Laravel testing with PHPUnit and Dusk, feature tests, unit tests, browser tests, factories, assertions. ALWAYS activate when: writing tests, tests/Feature/, tests/Unit/, tests/Browser/, running php artisan test...
Guides test-driven development with red-green-refactor cycle. Stores successful test patterns in EC. Use when implementing new features or fixing bugs with tests.
Ensures verification commands are run before claiming success. Checks EC for project-specific gotchas. Use before asserting tests pass, builds succeed, or bugs are fixed.
Verifies tests, reviews for EC memory storage, and presents merge options. Use when implementation is complete and ready to finish a feature branch.
Goのテストコード作成・修正が必要な時に使用するスキル。「テストコードを書いて」といった明示的な指示は当然、それ以外でも、テストコードの追加や修正が必要な場合は必ず使用する。
Run and debug Midnight contract tests using Vitest simulators. Use this skill when testing contracts, debugging test failures, or writing new tests. Triggers on "run tests", "test contract", "debug test", "test...
Use when reviewing test suites, after test runs pass, or when user asks about test quality
Run a live Looper-Go smoke test by creating a temporary project (PROJECT.md + to-do.json), executing looper for one iteration, observing output, and reporting results. Use when verifying looper-go behavior or d...
Run a live Looper-Go smoke test by creating a temporary project (PROJECT.md + to-do.json), executing looper for one iteration, observing output, and reporting results. Use when verifying looper-go behavior or d...
Use this skill when writing new features, fixing bugs, or refactoring C++20 code. Enforces test-driven development with Google Test/Mock, CMake/CTest integration, and 80%+ coverage via gcov/lcov.
Skill para desenvolvimento guiado por testes (Test-Driven Development)
Use Vercel's agent-browser CLI for automated browser testing and UI verification. Use when: (1) browser-based quality gates are required, (2) verifying UI behavior in the browser, (3) gathering screenshots or D...
Generate detailed executable test cases from specifications. Use when creating detailed test cases, expanding test specs, or generating TC-IDs. Triggers on keywords like "test cases", "generate tests", "detaile...
Use when the user asks to generate comprehensive feature documentation with verified test cases, create feature README with code evidence, or document a complete feature with test verification. Triggers on keyw...
Create or update EasyPlatform test specifications in docs/test-specs/{Module}/. Use when asked to create test specs, write test cases, document test scenarios, or generate Given-When-Then specifications. Trigge...
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.