Testing & QA

Unit tests, integration tests, E2E, QA, validation, and test automation

skills in category: 29,138
pages available: 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 browser

Browse testing & qa skills

Showing 313–336 of 29,138 skills

Verify Feature OutcomesAVerify after implementation that a feature achieved its required user/system outcomes. Use for goal-backward post-implementation verification that tests observable behavior rather than merely checking code existence.testinggoVotes: 0GitHub stars: 67
Validate Implementation PlanAValidate whether an implementation plan can achieve its stated outcome before execution. Use to check requirement coverage, task contracts, dependencies, data/artifact flow, testability, ownership, impact coverage, and executable ordering without checking whether implementation already exists.testinggoVotes: 0GitHub stars: 67
Test ReviewerAReview existing tests against the software and contracts they actually exercise. Use to assess whether a test has justified unique protection, detects consequential faults, tolerates valid refactors, earns its lifecycle cost, or deserves strengthening, replacement, consolidation, or removal consideration. Reviews are read-only and evidence-backed, including TDD and regression tests.testinggotestingVotes: 0GitHub stars: 67
Test DesignerASeparate required change validation from permanent test retention, then design maintenance-adjusted contract tests before writing them, including each TDD increment. Use when planning acceptance or regression evidence, selecting system/integration/unit boundaries and oracles, or deciding what evidence a software change needs. Produces a direct validation plan plus a risk-proportionate retained-test plan or explicit no-new-test decision, not production code or a passing-test claim.testinggotestingVotes: 0GitHub stars: 67
Evaluate Acceptance CriteriaAExecute structured acceptance checks and record their observed results for later comparison. Use to capture a pre-change baseline or a post-change verification state without treating expected nonzero baseline results as execution failure.testingVotes: 0GitHub stars: 67
Web Marketing ConsentAHow to use @owlmeans/web-marketing-consent — the browser half of @owlmeans/marketing-consent: the post-sign-in privacy-choices step (MarketingConsentBody for a host that owns its layout, MarketingConsentScreen as the plain frame), a reusable MarketingConsentPreferences settings-card body, appendMarketingConsent's login step and terms landing hook, and the MarketingConsentClientService (fail-open, signed-out-safe). Auto-invoked when wiring the marketing-consent screen into a web app, framing i...testinggoreactVotes: 0GitHub stars: 3
Web Marketing ConsentAHow to use @owlmeans/web-marketing-consent — the browser half of @owlmeans/marketing-consent: the post-sign-in privacy-choices step (MarketingConsentBody for a host that owns its layout, MarketingConsentScreen as the plain frame), a reusable MarketingConsentPreferences settings-card body, appendMarketingConsent's login step and terms landing hook, and the MarketingConsentClientService (fail-open, signed-out-safe). Auto-invoked when wiring the marketing-consent screen into a web app, framing i...testinggoreactVotes: 0GitHub stars: 3
Delegate To HermesARun bounded coding tasks through the Hermes CLI when Claude's usage window is exhausted or a cheaper model can handle a well-scoped subtask. Use for an explicitly isolated handoff, not as the default coding driver; Claude must review the diff and rerun checks before accepting any result.testingshellbashVotes: 0GitHub stars: 3
Php ExpertAProduction PHP 8.3+ house rules for naming, style, typed constants, Override attributes, PHP 8.4 gotchas, strict types, Composer constraints, exceptions, PHPUnit, and anti-patterns. Use when writing or reviewing PHP code.testinggophpVotes: 0GitHub stars: 2
IssueAImplement a Linear issue end-to-endtestinggobashVotes: 0GitHub stars: 2
ImproveAReview and improve code — fix bugs, harden security, optimize performance, improve readability and maintainabilitytestinggobashVotes: 0GitHub stars: 2
DebugADebug and fix failing tests or errorstestingpythonrustVotes: 0GitHub stars: 2
Burn Down AuditsDDrive the scripted bulk burndown of docs/AUDIT.md — one one-shot `claude -p` subprocess per role per finding (verify → implement → adversarial review → fix), orchestrated by tools/audit-burndown/ and built to run unattended. Use when the staged audit backlog is too large to vet-and-file as GitHub issues (hundreds of findings) and the user asks to burn it down in bulk, run the audit burndown, or launch/check on a run.testingtypescriptpythonVotes: 0GitHub stars: 7
TestingAFull testing guide — the three-tier strategy (Vitest unit, Playwright E2E, Maestro native smoke on Android + iOS), every test command, CI workflow triggers, and Maestro installation. Use before writing, running, or modifying tests, or when debugging CI test failures.testinggotestingVotes: 0GitHub stars: 7
Skills GuideAGrouped catalog of every Splotch skill — what each one does and how related skills chain together (the audit lifecycle, the PR flow, ADRs, handoffs). Use when asked what skills are available, which skill fits a task, or how skills relate — and to register a skill you just created, renamed, or deleted.testinggoawsVotes: 0GitHub stars: 7
Leave Pr ReviewASplotch conventions that augment (not replace) the built-in review flow when reviewing a pull request — check out the PR branch locally for offline diffs and to run the code and empirically verify critiques, anchor every finding to a diff file + line as you analyze, then post the surviving findings onto the PR as a single inline-comment review; invoking the skill is itself the authorization to post publicly, and mode overrides instead keep the findings in chat, file them as GitHub issues (eac...testingrustgoVotes: 0GitHub stars: 7
Improve Performance MatrixADrive Splotch's deployment-target performance matrix from current evidence to zero unexplained scoreable red cells on the release-gate rows through product improvements and faithful recaptures, keeping harness work subordinate to and immediately useful for a named product experiment. Ships each causal product cluster as its own reviewed PR, merged before the next cluster begins; an unattended run goes through ship-campaign profile=performance. Use for sustained performance improvement; use ca...testinggoawsVotes: 0GitHub stars: 7
Drive Pr To MergeableATake one open pull request from opened to mergeable — build the reviewer prompt, get an independent rival-agent review, address every thread, repeat that round at most once more, drive CI to green, reconcile conflicts, and return a shippable-or-leftovers verdict. Never merges. Use whenever an open PR needs the repo's standard independent-review and CI loop, standalone or as the current tip of a stack; the skills that open PRs (ship-issue, fix-audits, create-stacked-prs, improve-performance-ma...testingrustgoVotes: 0GitHub stars: 7
Capture Performance MatrixACapture Splotch's drawing, undo, and discrete-action performance suites across macOS web, physical or simulated iPad web/native, and physical or emulated Android web/native targets. Use when producing a deployment-target performance snapshot, comparing renderer architectures, validating a performance change across platforms, or refreshing the committed performance matrix.testingrustgoVotes: 0GitHub stars: 7
Burn Down Oversized CodeAPay the size caps back down to their soft targets — mode=files for the per-file max-lines cap, mode=functions for max-lines-per-function. Measures every covered unit against the cap ESLint resolves for it, has a proposer and an adversarial reviewer decide split-or-raise per unit, implements each split in its own worktree behind an independent commit check, retires stale per-file caps, and ships one themed PR with one commit per unit through drive-pr-to-mergeable. Use when asked to burn down, ...testinggonodeVotes: 0GitHub stars: 7
Burn Down Outdated DependenciesACheck package.json dependencies and GitHub Actions pins for updates (incl. majors), then upgrade them one at a time — read the migration guide, fix all usage, verify, and commit each on its owntestingtypescriptgoVotes: 0GitHub stars: 7
Burn Down Flaky TestsADrive Splotch's masked Playwright retry count toward zero using the rolling flaky digest, fixes verified under equal worker load, and narrowly tracked quarantine when a confirmed flake cannot be fixed. Use for a periodic E2E flake burndown, not for an ordinary single failing test.testingnodetestingVotes: 0GitHub stars: 7
Burn Down AuditsADrive the scripted bulk burndown of docs/AUDIT.md with isolated Codex subprocesses per role and finding (verify → implement → adversarial review → fix). Use when the staged audit backlog is too large to vet and file as individual GitHub issues, or when asked to launch, resume, supervise, pause, report on, or close out an audit burndown from Codex.testingrustgoVotes: 0GitHub stars: 7
Audit SessionARetrospective on the current session that files durable, recurring friction (finding, understanding, running, or changing code) as audit findings in docs/AUDIT.md so the repo's Claude tooling gets sharper over time. Use near the end of a working session, before /clear, or when asked to reflect on session friction.testingrustgoVotes: 0GitHub stars: 7