end-to-end-testing
Systematic E2E testing workflow with evidence capture and reporting. Use when running integration tests, validating complete user flows, capturing test…
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-21 00:11
Testing & quality
12,419 results
migrate-protractor-to-codeceptjs
Port a Protractor test suite to CodeceptJS 4. Trigger when the project contains `protractor.conf.{js,ts}`, `protractor` in `devDependencies`,…
migrate-testcafe-to-codeceptjs
Port a TestCafe test suite to CodeceptJS 4. Trigger when the project contains `.testcaferc.{json,js,ts,cjs}`, `testcafe` in `devDependencies`, test files…
pattern-test
Write and run pattern tests
debugging-output-and-previewing-html-using-ray
Use when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in…
scientific-publication
Best practices for iterative refinement of publication-quality scientific figures. Covers systematic improvement workflows, layout optimization, and ensuring…
flutter-add-widget-test
Use when writing widget tests, finding UI elements with finders, simulating user gestures, or testing widget state updates.
test-ui
[Testing] Use when you need full-site QA audit (accessibility, performance, security, SEO) with visual reports.
drupal-unit
Drupal Unit tests with UnitTestCase — testing isolated PHP logic with no Drupal bootstrap, mocking dependencies.
create-verification-skill
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for…
solo-audit
Use when "audit KB", "check frontmatter", "find broken links", "tag cleanup", "knowledge base quality", or docs need health check. Do NOT use for SEO audits…
xcodebuildmcp-test-boundary-review
Use when reviewing XcodeBuildMCP tests for correct unit, snapshot, schema, smoke, and external process boundaries.
tdd
Use only when the user explicitly names tdd or an upstream task explicitly invokes it to implement a feature or bug fix test-first. Execute vertical…
verify
Use when about to say anything that implies success — "done", "fixed", "passing", "works", or any paraphrase — and before committing, opening a PR, closing a…
pentest-supply-chain
Software supply chain security — dependency confusion, CI/CD pipeline attacks, lockfile integrity, and build artifact verification.
testing-mobile-apps
Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run…
daily-auditor
The read-only morning audit: last 7 complete days vs the prior 7, wasted budget, fading ads, starved tests, pixel problems, one next test. Max 5…
py-quality-setup
Configure ruff, mypy, and basedpyright for Python 3.13 projects. Use when setting up linters and type checkers in pyproject.toml and pyrightconfig.json.
moli-cdp-server
Start Moli's CDP server and connect Playwright, Puppeteer, or raw CDP clients. Use to run a headless-browser CDP endpoint, replace a Chromium process, attach…
rails-testing
Apply Rails testing standards with Minitest, fixtures, and pragmatic coverage boundaries. Use when creating tests, reviewing test quality, or improving flaky…
code-review
Multi-agent code review with parallel specialized reviewers, architecture validation, challenge validation, and durable handling of previously decided…
qa-code-reviewer
The independent review step, the second-to-last step in the QA process. After qa-test-runner finishes execution, review the code itself from an independent perspective—check architecture, security, concurrency correctness, data consistency, regression risk, and test coverage gaps—without being influenced by the executor's conclusions. Produce code-review.json (containing severity-graded findings and readiness constraints), and…
qa-context-profiler
QA upstream phase — build a factual profile and environmental evidence for the repository. Triggered when you need to collect a module's code context, index existing cases and tests, check front-end/back-end service reachability, or prepare an environment snapshot. Collect facts only; do not do risk analysis, write test cases, or judge quality. Usually executed as the first phase under the scheduling of quality-assurance-agent.…
qa-test-runner
After spec-task and the test scripts are ready, execute them one by one, classify failures, fix the minimal root cause, collect evidence, and run the completion gate. You are only responsible for "running"—you do not generate reports, review code, or decide Ready. Review is left to qa-code-reviewer; reports and decisions are left to qa-report-generator. Not applicable: report generation, code review, test case design.