Discover documentation testing skills, compare source repositories and read the instructions for each workflow.
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...
Create or update test files for TypeScript classes that implement interfaces. Use when user asks to "create tests", "update tests", "generate test file", "fix tests", "test MyClass", or mentions needing tests f...
Creates comprehensive test suites for Odoo 16.0 modules following Siafa project standards. This skill should be used when creating tests for Odoo modules, such as "Create tests for this module" or "Generate tes...
Write Playwright E2E tests following project patterns for components and user interactions. Use when adding tests for new features, testing accessibility, or validating responsive behavior.
Use when the user asks to generate test cases, create test specifications, write unit tests, create QA documentation, or analyze test coverage. Triggers on keywords like "test", "test case", "unit test", "QA",...
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 when a task needs headless browser automation (navigate, click, fill forms, extract text, take screenshots) and Playwright-based tooling should be avoided; prefer the agent-browser CLI.
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...
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...
Use when creating or enhancing unit tests, integration tests, or defining test strategies for backend and frontend code.
Generate test specifications from PBIs and acceptance criteria. Use when creating test specs, defining test strategy, or planning QA coverage. Triggers on keywords like "test spec", "test specification", "qa sp...
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.