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,889–3,912 of 31,122 skills
- Antigravity Ai ProductYou are an AI product engineer who has shipped LLM features to millions of users. You've debugged hallucinations at 3am, optimized prompts to reduce costs by 80%, and built safety systems that caught thousands of harmful outputs. You know that demos are easy and production is hard.Votes: 0GitHub stars: 2
- Ts TestingGenerates dense law-driven test suites for Effect modules via algebraic PBT using Vitest, @effect/vitest, fast-check. Enforces 175 LOC cap, 95% per-file coverage, mutation kill-ratio via Stryker. Use when writing/reviewing spec files, adding coverage, generating property tests, debugging flakes, or scaffolding unit/integration/E2E tests from templates.Votes: 0GitHub stars: 2
- Hooks BuilderCreates Claude Code hooks executing shell commands, prompt evaluations, or multi-turn agents at 15 lifecycle events. Use when building PreToolUse validation, PostToolUse formatting, PermissionRequest auto-approval, Stop/SubagentStop evaluation, TeammateIdle prevention, TaskCompleted gating, Setup provisioning, SessionStart context injection, or deterministic agent control via blocking/non-blocking hooks.Votes: 0GitHub stars: 2
- Web QaAutonomous web app QA — Playwright E2E + visual regression + axe-core accessibility, with auto-generated test scenarios from git diff or text instructions. Project-portable (each project owns its `.web-qa/` state). Use when the user asks to test a website, verify a frontend feature, run regressions, or audit a11y.Votes: 0GitHub stars: 5
- Frontend Ui AgentOwns the frontend render layer — components, pages, utility helpers, and CSS. Runs in parallel with frontend-api-agent on full-stack changes. Also the sole agent for cheap/styling-only changes. Owns apps/frontend/src/components/, pages/, utils/, and all CSS.Votes: 0GitHub stars: 2
- Rtl Area TimingUse when optimizing RTL microarchitecture for area or clock frequency (Fmax), a design is too big to fit or too slow to meet timing, a wide multiply or barrel shifter is the critical path, or a "compute everything and select" datapath is too largeVotes: 0GitHub stars: 21
- Rohd Rtl GotchasUse when building or testing RTL in ROHD (Dart), rohd_bridge, or rohd_hcl and hitting hierarchy-violation errors, "Bad state: No element" at sim setup, co-simulation failures, SystemVerilog emission name mismatches, or unexpected register read latencyVotes: 0GitHub stars: 21
- Differential VerificationUse when verifying a hardware DUT (a CPU core, FPGA, or netlist) against a golden reference model, building coverage-guided fuzzing, or detecting where silicon diverges from a simulator like Spike, an emulator, or SPICEVotes: 0GitHub stars: 21
- Implement SpecImplement a single phase of a spec. Use when given a spec file and a phase number to implement.Votes: 0GitHub stars: 896
- Paper PipelineOrchestrate the complete post-first-draft polishing pipeline for an academic LaTeX paper by invoking five existing skills in fixed order: (1) paper-polish, (2) paper-self-revise, (3) paper-style, (4) paper-polish again, (5) reference-verify. Trigger when user says \"paper pipeline\" / \"paper-pipeline\" / \"论文流水线\" / \"全流程打磨\" / \"一条龙打磨\" / \"初稿打磨\" / \"full polish pipeline\" / \"run the whole pipeline\", or wants the entire post-draft polishing sequence run on a paper folder. Use this skill ...Votes: 0GitHub stars: 2
- Test Strategy DocumentCreate a production-ready Testing Strategy and QA Execution Plan. Covers testing levels (unit, integration, E2E, performance), mocking boundaries, test environment matrix, code coverage thresholds, and automated CI pipeline runsheets. Use when establishing a QA framework for a new system or feature set.Votes: 0GitHub stars: 6
- SnapUse when you just want screenshots of every screen saved as image files — capture all screens/states/variants of a locally runnable app, no QA analysis, no findings, just the pictures. Triggers on "스크린샷 다 찍어줘", "모든 화면 캡쳐해서 저장", "capture all screens", "screenshot everything".Votes: 0GitHub stars: 2
- ScriptifyUse when asked to turn a QA or capture flow into a reusable static shell script so it can be re-run without an agent — generate a repo-native `.sh` that launches, seeds, and captures screenshots/video deterministically. Triggers on "정적 스크립트로 만들어줘", "sh 파일로", "에이전트 없이 재실행", "capture script 생성".Votes: 0GitHub stars: 2
- ReproUse when you want a video that reproduces a flow or an error/bug and saves the clip — a shareable recording of the steps that trigger a problem. Triggers on "오류 영상으로 남겨줘", "버그 재현 영상", "record a repro video", "capture a video of this bug".Votes: 0GitHub stars: 2
- PreflightUse when starting any app QA or test run, to check whether a repo can be run and tested locally — detect project type, verify the toolchain, discover how it runs and where screenshots/media should go — before capturing or testing. Triggers on "테스트 가능한 환경인지", "환경 점검", "preflight", "can I run this locally".Votes: 0GitHub stars: 2
- CasewrightUse when asked to generate or write automated test cases for a locally runnable app — turn user flows, routes, or QA findings into reusable tests (e2e, integration, unit, regression) in the repo's own test framework. Triggers on "테스트 케이스 만들어줘", "테스트 작성", "회귀 테스트", "generate tests", "write test cases", "e2e 테스트 생성".Votes: 0GitHub stars: 2
- BugsweepUse when asked to QA an app end to end, run a full-path / 전체 경로 / 전수 QA, capture screenshots of every screen, or verify all user flows (signup, login, every feature) of a locally runnable web, iOS, Android, API, or monorepo project. Triggers on "전수 QA", "모든 화면 캡쳐", "직접 써보고 버그 찾아줘", "full QA pass".Votes: 0GitHub stars: 2
- BreachsweepUse when asked to security-test, pentest, or find vulnerabilities in a locally runnable app you own — auth/authorization (IDOR), input validation (injection), secret exposure, security headers, insecure cookies/CORS. Triggers on "보안 점검", "취약점 찾아줘", "security audit", "pentest my app".Votes: 0GitHub stars: 2
- Flutter TestingDesign, write, or review Flutter unit, widget, golden, and integration tests. Use for test strategy, regressions, fakes, async UI behavior, and end-to-end flows; use device testing for operational emulator or hardware control.Votes: 0GitHub stars: 7
- Qa ExpertYou are a quality assurance specialist with expertise in test automation, testing strategies, and quality processes. You design and implement comprehensive testing that catches bugs before production.Votes: 0GitHub stars: 2
- crud-stackBuild or extend a multi-tenant, role-scoped, audited web app on a generic-CRUD architecture — Express + Sequelize behind one crudThat factory with per-model controller hooks, a no-build-step vanilla JS frontend, a shared rules module both sides run, and a three-container Docker/Traefik/MySQL deployment. Use when starting a new project of this shape, or when adding a model, controller, route, view, test or environment variable to one. Covers the CRUD factory and its hooks, the access model, pr...Votes: 0GitHub stars: 3
- TestingThis skill should be used whenever writing, reviewing, or fixing tests — when the user asks to "write tests", "add tests for X", "test this function/class", "improve test coverage", "review my tests", "why is this test flaky", "should I mock this", "how do I test X", mentions TDD or characterization tests, asks how to test code that has no tests or seems untestable, or when Claude has just written production code and is about to add tests for it. Provides test-design fundamentals, a test-doub...Votes: 0GitHub stars: 2
- Test PlanningUse when turning a behavior specification and codebase recon into an approved test plan — choosing test cases and coverage depth per behavior, picking the right scope (unit, integration, contract, schema, property, UI, E2E), justifying every choice, running an adversarial critique of the plan, and reviewing it with the user before any test is written. Invoked by /test-write between extraction and authoring.Votes: 0GitHub stars: 2
- Test AuditingUse when assessing a whole repository's test suite rather than specific test files — finding where protection is weakest, diagnosing systemic problems across the suite, ranking modules by risk against the strength of their tests, and producing a map that says where to spend test effort next. Invoked by /test-audit. For per-test defects in a known set of files, use /test-review instead.Votes: 0GitHub stars: 2