All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 31,122
- 1,297
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,385–3,408 of 31,122 skills
- TestgenGenerate tests with expert routing, framework detection, and auto-TaskCreate. Triggers on: generate tests, write tests, testgen, create test file, add test coverage.Votes: 0GitHub stars: 211
- SpawnGenerate PhD-level expert agent prompts for Claude Code. Creates comprehensive 500-1000 line agents with detailed patterns, code examples, and best practices. Triggers on: spawn agent, create agent, generate expert, new agent, agent genesis.Votes: 0GitHub stars: 211
- Runtime Routing And RenameThis scenario validates advisor routing for explicit AI Council prompts.Votes: 0GitHub stars: 36
- Runtime Routing And RenameVerify scorer coverage for deep-ai-council.Votes: 0GitHub stars: 36
- Sk Create DiffLocal, Git-free before/after review of an edited document (text, Markdown, HTML, DOCX, text PDF) as a self-contained HTML report.Votes: 0GitHub stars: 36
- Sk Create BenchmarkAuthor MCP-promotion, behavior, and model-benchmark artifacts; route the Lane A authoring guide.Votes: 0GitHub stars: 36
- Sk Code Webflowsk-code WEBFLOW surface: frontend evidence (CSS/HTML/JavaScript standards, implementation and performance patterns, CDN deployment, browser debugging and verification) plus shared implement/debug/verify workflow doctrine.Votes: 0GitHub stars: 36
- Sk Create DiffLocal, Git-free before/after review of an edited document (text, Markdown, HTML, DOCX, text PDF) as a self-contained HTML report.Votes: 0GitHub stars: 36
- Sk Create BenchmarkAuthor MCP-promotion, behavior, and model-benchmark artifacts; route the Lane A authoring guide.Votes: 0GitHub stars: 36
- Sk Code Webflowsk-code WEBFLOW surface: frontend evidence (CSS/HTML/JavaScript standards, implementation and performance patterns, CDN deployment, browser debugging and verification) plus shared implement/debug/verify workflow doctrine.Votes: 0GitHub stars: 36
- Agent DebugUser-invoked fresh-perspective debugger: 5-phase root-cause methodology, never auto-dispatched.Votes: 0GitHub stars: 36
- Test ReliabilityGovern flaky tests and suite reliability: rerun-pass verdicts, root-cause classes, quarantine, retry semantics, health metrics. Not for: in-run failures (e2e/api), triage, confirmed bugs. 治理 flaky 测试与套件可靠性：时好时坏/重跑变绿判定、根因四分类、隔离门禁、重试诚实语义、健康度。不用于：执行中单条失败（e2e/api）、批量分流（triage）、已确认 Bug（bug-analysis）。Votes: 0GitHub stars: 33
- Qa MemoryMaintain the .qa/ knowledge base of cross-session QA knowledge (quirks, flaky verdicts, defect patterns, contract changes); read before test tasks. Not for: pipeline state, case files (test-case-writing). 维护被测项目 .qa/ 跨会话知识库（环境怪癖、flaky、缺陷模式、契约变更）读写治理；任务前先读取。不用于：流水线状态、用例文件读写（test-case-writing）。Votes: 0GitHub stars: 33
- Review Pr QueueWork a backlog of open pull requests down to merged — read the review comments that are actually there, fan out one fixer per PR in its own worktree, verify each with an adversarial reader from another model family, and merge in an order that avoids conflicts. Use on "address the comments on these PRs", "review and merge the queue", "clear the PR backlog", when a repo has accumulated more open PRs than anyone wants to read, or when review feedback exists but nobody has acted on it.Votes: 0GitHub stars: 13
- Playwright DebuggerUse when a Playwright end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Playwright spec, TimeoutError, broken or ambiguous selector, post-deploy suite failure, retry-only flake, hydration or timing race, or a passes-locally-but-fails-in-CI split. Accept error messages, playwright-report/ or HTML reports, trace.zip, screenshots, and CI artifacts identified by a GitHub owner/repo slug plus run id. Distinguish product regression...Votes: 0GitHub stars: 16
- E2e ReviewerUse when reviewing Playwright or Cypress E2E specs, Page Objects (POM), PRs, pull requests, patches, diffs, or changed test files — asked to review tests, audit test quality, or find weak, flaky, or silently-passing tests; when tests pass CI but prove nothing or miss bugs; when auditing missing awaits, vacuous or always-passing assertions, anti-patterns, or coverage gaps. Not for debugging a test that is currently failing at runtime (use playwright-debugger / cypress-debugger).Votes: 0GitHub stars: 16
- Cypress DebuggerUse when a Cypress end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Cypress spec, Timed-out-retrying command, unresolved selector, cy.intercept alias or request race, suite-breaking hook, retry-only flake, hydration or timing race, or a passes-locally-but-fails-in-CI split. Accept mochawesome or JUnit reports, errors and stacks, screenshots, videos, and CI artifacts such as a GitHub run id. Distinguish product regressions fr...Votes: 0GitHub stars: 16
- Producing Visual EvidenceProduces inspected, state-indexed evidence from real UI. Use when a visual or interaction claim needs reproducible screenshots, recordings, or GitHub review evidence.Votes: 0GitHub stars: 64
- Inventorying Codebase PatternsBuilds replayable, source-derived catalogs with drift checks. Use when a migration or audit needs a trustworthy inventory across files.Votes: 0GitHub stars: 64
- Desloping Code ChangesTests whether code-change complexity is justified by behavior and local contracts. Use for a focused craft review of copied styling, wrappers, names, types, or abstractions in a diff.Votes: 0GitHub stars: 64
- Pr ReadyVerify a branch, resolve in-scope failures, and prepare its PR description; publish only when requested.Votes: 0GitHub stars: 56
- Refactor Move Logic To AggregateMove business logic from handlers, services, or endpoints into aggregate methods where it belongs. Detects "logic leak" — validation, calculations, state transitions, and business rules scattered outside the domain model — and refactors them into rich aggregate methods with proper invariants. Use when the user says "move logic to aggregate", "handler is too fat", "fix logic leak", "enrich my aggregate", "make aggregate rich", "handler has too much logic", "anemic domain model", or when an aud...Votes: 0GitHub stars: 46
- Generate Test ScaffoldGenerate test scaffolds from Protean domain definitions. Analyzes existing aggregates, commands, events, handlers, value objects, and entities to produce focused pytest test stubs for user-written business logic - aggregate behavior, state transitions, invariants, event raising, handler orchestration, and end-to-end flows. Follows Protean's testing pyramid (domain unit tests as majority). Does NOT generate tests for framework-guaranteed behavior (VO immutability, field validation, registratio...Votes: 0GitHub stars: 46
- Coverage AnalysisAnalyze Protean domain code to identify untested code paths and generate missing tests. Catalogs all testable elements (aggregate methods, invariants, events, handlers, value object operations, entity management) from domain definitions, compares against existing tests, produces a gap report with severity classification, and generates missing tests using generate-test-scaffold patterns. Use when the user asks to "find untested code", "analyze test coverage", "check what's missing tests", "ide...Votes: 0GitHub stars: 46