All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 29,138
- 1,215
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse testing & qa skills
Showing 337–360 of 29,138 skills
- Address Pr ReviewTriage and address every reviewer comment on a pull request — validate each one against the current code, fix the valid ones and reply with the solution, reply to and resolve the invalid ones with the rationale. Use when asked to address, respond to, or work through the comments/feedback/review received on a PR. To produce a review of a PR (author the critique), use leave-pr-review instead.Votes: 0GitHub stars: 7
- X4 Xml PatchingUse when writing, editing, reviewing or validating ANY X4 XML — diff patches, mod files, overlays, wares, macros, libraries, md/ or aiscripts/. Carries the selector, merge-tree and load-order gotchas that make a patch silently no-op, where a given fix belongs, and how to validate it before an in-game test cycle. Invoke before the first edit, not after the patch fails.Votes: 0GitHub stars: 2
- IntentCover the skill's parsing, scaffolding, checks and index with an executable suite that runs in CI.Votes: 0GitHub stars: 17
- Ia Nav AdrUse when changing information architecture, section placement, navigation YAML, slugs, URLs, page identity, /ops rules, ADRs, or contribution rules.Votes: 0GitHub stars: 20
- Openclaw Backup VerifyValidate OpenClaw backup archives and restore readiness with repeatable checks. Use when users ask to confirm backup integrity, test migration safety, or verify that a backup file is usable before moving systems.Votes: 0GitHub stars: 2
- Parallels Discord RoundtripRun the macOS Parallels smoke harness with Discord end-to-end roundtrip verification, including guest send, host verification, host reply, and guest readback.Votes: 0GitHub stars: 2
- Openclaw Qa TestingRun, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.Votes: 0GitHub stars: 2
- Openclaw Parallels SmokeEnd-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.Votes: 0GitHub stars: 2
- Validate Ul Fund DataValidate quarterly UL fund Excel extracts before analysis. Use whenever a quarterly extract is uploaded, mentioned, or suspected to be malformed, including requests to check, QA, sanity-check, or verify it. Run before analysis even when validation is not explicitly requested.Votes: 0GitHub stars: 5
- Spontaneous Testing For ExcelRun the plain-language tests held in the `tests` table on the `TEST` sheet of an Excel workbook. Read each description, check it against the workbook by reading cells, then write an evidence trail into process and a PASS / FAIL / INCONCLUSIVE / BLOCKED / ERROR verdict into result. Use this whenever a workbook has a TEST sheet or a tests table, and whenever someone asks to run the tests, run the checks, run the test suite, run the validations, or QA, verify, validate or sanity-check an Excel w...Votes: 0GitHub stars: 5
- Historic Eiopa Yield CurveAnswer any question about historic EIOPA risk-free rate (RFR) yield curves - a spot rate for a country and tenor at a reference date, a whole term structure, a tenor through time, countries side by side, implied forwards, discount factors, the Solvency II stressed curves, or curve parameters (UFR, LLP, alpha, CRA, VA). It carries the full published history with it - every monthly release since 2014-12-31, all curves, terms 1-150 years, no_VA and with_VA - so it needs no dataset, database, net...Votes: 0GitHub stars: 5
- Civiltekk Test Generation SkillMulti-route test generation. framework-matrix: language/framework detection plus the 6-step generation lifecycle. python: pytest scenario taxonomies and file template. nextjs: Next.js 16 render/action/route patterns. Triggers: test generator, generate tests, pytest test files, Next.js unit tests, Server Components, Server Actions, API route tests. Not for running or fixing existing failing suites.Votes: 0GitHub stars: 6
- Frontend Walkthrough对已实现的前端页面做真实操作走查:遍历状态矩阵与交互路径、检查反馈与容错、体检加载性能,产出带证据的优化与补充清单。触发:"前端走查"、"体验一下这个页面"、"点一遍看看"、"前端页面有什么问题"。Votes: 0GitHub stars: 2
- Kb Report[KB] Read the knowledge base's own logs and render the report — what agents asked, what the base could not answer, which answers were useless, and the §15 acceptance verdict. Run it before deciding what to build for the base next, and to judge a check wave.Votes: 0GitHub stars: 2
- Sharp Pairwise Reduction Pgm Hypothesis TestingUse when bounding PGM error in quantum state discrimination.Votes: 0GitHub stars: 3
- Riemannian Private InferenceUse for private inference on manifold-valued optimization.Votes: 0GitHub stars: 3
- Nca Deltarule Fast Memory AdaptationUse for gradient-free online task adaptation via NCA cellwise fast memory.Votes: 0GitHub stars: 3
- TestUse this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders.Votes: 0GitHub stars: 251
- Feat TestUse when the user wants tests planned for existing code or a test audit — unit, integration, E2E scenarios exportable to Playwright, playwright-cli UI checks, a coverage matrix — 'criar testes para o UserService', 'plano de testes E2E do login', 'auditar a cobertura'. Writes .planning/feat/features/{slug}/plan.md. Do NOT use for code review (feat-review), for implementing features (feat-feature) or to run an existing plan (feat-exec).Votes: 0GitHub stars: 3
- Feat QuickUse when the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).Votes: 0GitHub stars: 3
- Feat FrontendUse when the user wants a UI-only action plan — components, pages, composables/hooks, state, forms and their E2E coverage — 'plano de frontend para a tela X', 'plan the settings page'. Writes .planning/feat/features/{slug}/plan.md with E2E scenarios and playwright-cli checks. Do NOT use for API/database work (feat-backend), full features (feat-feature), writing code (feat-exec) or UI review (feat-review).Votes: 0GitHub stars: 3
- Feat FeatureUse when the user wants a full feature action plan (backend + frontend + tests) with the PWDEVIA 7-question method before any code is written — 'planejar a feature X', 'criar plano de feature', 'plan the user CRUD'. Interviews the human (max 2 rounds) and writes .planning/feat/features/{slug}/plan.md. Do NOT use to write code (feat-exec), for small 1–3 file changes (feat-quick), backend-only or UI-only scope (feat-backend / feat-frontend), tests for existing code (feat-test) or code review (f...Votes: 0GitHub stars: 3
- Feat BackendUse when the user wants a backend-only action plan — API endpoints, services, models, migrations, jobs and their tests — 'plano de backend para o endpoint X', 'plan the orders API'. Writes .planning/feat/features/{slug}/plan.md with the PWDEVIA method. Do NOT use for UI work (feat-frontend), full features spanning backend and UI (feat-feature), writing code (feat-exec) or quick 1–3 file fixes (feat-quick).Votes: 0GitHub stars: 3
- Web Test AutomationUse when designing, choosing tools for, or writing automated tests for web applications — E2E and UI tests, visual regression, web accessibility (axe-core), API testing inside browser flows, flaky-test debugging, page object model, and CI integration. Playwright-first, with Cypress and Selenium guidance and migration paths. Triggers on web testing, browser test, E2E, Playwright, Cypress, Selenium, page object, locator, flaky test, visual regression, accessibility testing, network mocking, CI ...Votes: 0GitHub stars: 10