All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 31,095
- 1,296
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 3,097–3,120 of 31,095 skills
- Verify TicketUse when verifying a tracker ticket (Jira/Azure DevOps/GitHub issue) against the app in this Vexa repo — reproducing a reported bug or confirming a fix, capturing evidence screenshots, writing a Playwright test, and posting the verdict. Triggers include "verify ABC-123", "check this ticket", "is ABC-123 fixed", "reproduce this bug", "automate ABC-123".Votes: 0GitHub stars: 2
- Setup VexaUse when setting up this Vexa framework for a new project — configuring a fresh clone to the user's own app in one go (project name, app URL, login selectors, .env, dependencies, starter test). Triggers include "set up vexa for my project", "bootstrap this framework", "configure vexa for my app", "one-command setup".Votes: 0GitHub stars: 2
- K6 PerformanceModern load testing with k6 including thresholds, scenarios, and custom metrics. Use when writing, reviewing, or debugging a k6 script — general k6 syntax and patterns, not Vexa-specific scaffolding.Votes: 0GitHub stars: 2
- QaUse when the user starts, continues or retests a QA test session — «/qa <link|description>», «test this task», «run a test session», «retest session X», a tracker task handed over for verification; also triggers on the Russian «протестируй задачу», «проведи тест-сессию», «ретест по сессии X».Votes: 0GitHub stars: 3
- Qa SetupUse when qa-cube needs wiring into a project or its profile needs updating — «/qa-setup», «set up qa for this project», «qa onboarding», or when /qa could not find `.claude/qa-profile.md` or reported that the profile is behind the contract; also triggers on the Russian «настрой qa для проекта», «qa-онбординг».Votes: 0GitHub stars: 3
- Test IntegrityCatches silent test tampering — test edits that hide a behavior change rather than track a genuine spec change. Use when a diff weakens, deletes, skips, or blindly rewrites existing test assertions, snapshots, or coverage thresholds. Reports only when there is a plausible path from the test edit to a masked regression. Excludes cosmetic test refactors, style, and production-only bugs.Votes: 0GitHub stars: 3
- Test SelectionUse this skill when someone describes a specific code path, feature, or bug and asks what kind of test to write for it — or when an audit or strategy engagement surfaces a testing gap and needs a recommendation for where to start. Trigger on "what test should I write for this", "unit or integration test for X", "our E2E suite is too slow", or similar scenario-specific testing questions. Standalone from the audit and strategy skills — no prior audit is required to use it.Votes: 0GitHub stars: 4
- Test ReviewUse this skill to review test code — not what test to write, but whether a test already written is any good. Trigger on "review this test", "is this test any good", "review my test suite", "does this test actually test what it claims", "should this be a unit test instead", or when a code review (including the built-in code-review skill) touches test files and test-specific judgment is needed. Standalone — no prior audit is required, and it complements rather than replaces the built-in code-re...Votes: 0GitHub stars: 4
- Refinement AdvisorUse to decide which refinement and hardening tools are worth running on a set of changes — refine, crap-analyzer, arch-check, introversion scan, mutation testing, TLA+ model checking, Lean proofs — and on which files, with the invariant to check. Triggers — "/engineer.refinement-advisor", "what should we harden", "which checks fit this diff", "is this worth TLA+ / Lean", "should we model-check this", "how do I harden this change". Called by /engineer.harden at CP8; also usable ad hoc on any d...Votes: 0GitHub stars: 150
- HardenUse after a feature passes Light Verify (CP7), to prove the tests actually catch bugs and, where the code warrants it, to formally check its invariants — Checkpoint 8. Runs the refinement-advisor, then the picked tools — introversion scan, mutation testing, and opt-in TLA+ / Lean verification. Triggers — "/engineer.harden", "harden this feature", "Checkpoint 8", "which hardening does this need", "formally verify the feature".Votes: 0GitHub stars: 150
- Buying Stuffhelps choose what to buy and where to buy it, based on the user's priorities, budget, and location. use for shopping research, purchase recommendations, and comparing items before buying; checks quality, reliability, sellers, prices, delivery, and returns.Votes: 0GitHub stars: 64
- Spine SimplifyPost-feature clarity pass — collapse needless indirection, delete dead code, flatten nesting, surface duplicated logic, fix altitude mismatches. Behavior-preserving only. Use when asked to "simplify this", "clean up this code", "reduce complexity", "this feels over-engineered", or "tidy up after the feature".Votes: 0GitHub stars: 73
- Automated A11y Testing Axe CoreImplements automated accessibility testing across the testing pyramid using axe-core engine with jest-axe, @axe-core/playwright, pa11y-ci for unit/E2E/CI integration and WCAG violation detection.Votes: 0GitHub stars: 6
- Openspec OnboardGuided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work. Also use when the user says "openspec onboard" or "opsx onboard".Votes: 0GitHub stars: 17
- VerificationRun verification checklist before marking work complete. Use when verifying task completion, checking deployment success, or when user mentions 'verify', 'check work', 'confirm complete', 'verification'.Votes: 0GitHub stars: 2
- Plan GenerationGenerate implementation plans for projects. Use when creating a plan, drafting implementation steps, or when user mentions "create plan", "implementation plan", "planning phase", or "plan this project".Votes: 0GitHub stars: 2
- Test Driven DevelopmentRed-Green-Refactor cycle with Amazon's test pyramid (80% unit, 15% integration, 5% e2e). Coverage gates, DAMP over DRY in tests, canary tests in production.Votes: 0GitHub stars: 15
- Pipeline SafetyCI/CD pipeline safety with automated gates, deployment blockers, alarm checks, and one-click rollback.Votes: 0GitHub stars: 15
- Diagnosing BugsBuild a reproducible feedback loop for hard bugs or performance regressions. Use when reproduction is missing or unreliable.Votes: 0GitHub stars: 10
- FixturesUse when the user asks "review my changes" / "is this safe to merge" / "what could break". Reads the diff and the changed files first, surfaces what was found + named risks, runs tests, then delivers the verdict — section by section with confirmation gates, not as one dump. Refuses to claim safe-to-merge without fresh verification evidence.Votes: 0GitHub stars: 7
- FixturesUse when the user asks "review my changes" / "is this safe to merge" / "what could break". Reads the diff and the changed files first, surfaces what was found + named risks, runs tests, then delivers the verdict — section by section with confirmation gates, not as one dump. Refuses to claim safe-to-merge without fresh verification evidence.Votes: 0GitHub stars: 7
- FixturesUse when the user asks "review my changes" / "is this safe to merge" / "what could break". Reads the diff and the changed files first, surfaces what was found + named risks, runs tests, then delivers the verdict — section by section with confirmation gates, not as one dump. Refuses to claim safe-to-merge without fresh verification evidence.Votes: 0GitHub stars: 7
- FixturesUse when the user asks to plan QA for a story, ticket, or piece of work before coding starts. Identifies named risks anchored in the change shape, then proposes a smallest useful test set tied to those risks. Lighter-weight than sumo-qa-creating-test-plan; no formal entry/exit criteria.Votes: 0GitHub stars: 7
- Using Sumo QaMUST be called first for any QA-shaped request. Triggers include test plan, test strategy, test approach, regression scope, risk-based testing, exploratory testing, code review, safety-to-merge, scaffold tests, TDD, mutation testing, find test data, validate test data, QA audit, test pyramid, "how do I test X", "is this safe to merge", "what should I check". Also development-framed testing asks ("I'm adding X, how should I test it", "what tests do I need", "cover the edge cases", "write the f...Votes: 0GitHub stars: 7