Total 53,735 skills, Testing & QA has 1918 skills
Showing 12 of 1918 skills
PHPUnit testing best practices and conventions guide. This skill should be used when writing, reviewing, or refactoring PHPUnit tests to ensure consistent, maintainable, and effective test suites. Triggers on tasks involving test creation, test refactoring, test configuration, code coverage, data providers, mocking, or PHPUnit XML configuration.
Review implementation quality — catch visual bugs, placeholder text, broken links, and spec drift that functional tests miss. Use this after tests pass to ensure the output looks right, not just works right.
Execute YAML test plan, stop on first failure, output rich debug prompt
Dry-run Stacks contract calls against mainnet state before broadcasting — catches errors, prevents wasted gas
Use when authoring or normalising a specialist skill, or preparing to ship a feature or release — defines the seven evidence categories every specialist skill must declare against and provides the canonical Release Evidence Bundle template. The contract spine that turns scattered validation skills into a coherent ship-readiness check.
Zephyr Scale integration. Manage Requirements, Projects, Users, Roles. Use when the user wants to interact with Zephyr Scale data.
Command-line interface for CloudAnalyzer — Agent-friendly harness for CloudAnalyzer, a QA platform for mapping, localization, and perception outputs. Supports 27 commands across 8 groups: point cloud evaluation, trajectory evaluation, ground segmentation QA, config-driven quality gates, baseline evolution, processing, visualization, and interactive REPL.
Background knowledge for droid-control workflows -- not invoked directly. True-input driver mechanics for real terminal emulator automation via headless Wayland compositor.
Systematically add test coverage for all local code changes using specialized review and development agents. Add tests for uncommitted changes (including untracked files), or if everything is commited, then will cover latest commit.
Write, update, or review Dify end-to-end tests under `e2e/` that use Cucumber, Gherkin, and Playwright. Use when the task involves `.feature` files, `features/step-definitions/`, `features/support/`, `DifyWorld`, scenario tags, locator/assertion choices, or E2E testing best practices for this repository.
Expert performance testing and optimization specialist focused on measuring, analyzing, and improving system performance across all applications and infrastructure
Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.