Testing & QA

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

skills in category: 29,816
pages available: 1,243

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 769–792 of 29,816 skills

DebuggingADebugging (source maps, cache, test failures)testingtypescriptbashVotes: 0GitHub stars: 9
Test PlanAGenerate a comprehensive testing plan based on the current branch changes or a specific PR.testingtypescriptgoVotes: 0GitHub stars: 1,915
ReviewAReview PR(s) using the comprehensive review guidelines.testingtypescriptgoVotes: 0GitHub stars: 1,915
85 Ios Simulator SkillAUse when iOS app building, navigation, and testing - 嵌入式配套 iOS 应用测试（低优先级）。testingtestinggitVotes: 0GitHub stars: 2
57 Playwright Scraper SkillAUse when Playwright 反爬虫抓取 - 芯片规格书、驱动下载页面抓取。testingVotes: 0GitHub stars: 2
Plan Execution SkillBExecute PLAN.md phase-by-phase — parse phases and N.M steps, delegate, tick progress. Modes: --soft interactive; --gate (default for /run-plan) verification gate, fix-on-fail, per-phase commit+push; --update branch-detected checkbox sync. Triggers: run-plan, execute plan, automation loop, implement PLAN-*.md, update plan progress.testingrustgoVotes: 0GitHub stars: 6
Plan Execution Inline SkillAExecute PLAN.md phase-by-phase fully in-session — zero worker subagents. Same --gate loop as plan-execution-skill (tiered verification gate, fix-on-fail, per-phase commit+push) with testing, linting, docs, and responsive audit routed to the inline skills. Triggers: run plan inline, inline plan execution, implement PLAN-*.md without subagents.testinggobashVotes: 0GitHub stars: 6
Open3dAUse when registering overlapping point-cloud scans into one frame, optimizing a multiway pose graph, reconstructing a Poisson surface, or reviewing Open3D registration artifacts and their validators.testingpythongoVotes: 0GitHub stars: 33
Infra ContextAHow the system under test is built, run and deployed: its architecture and external services, the backend and frontend stacks with their run and test commands, the auth flow, the environments and their URLs, the CI/CD pipelines, and the non-functional budgets it must hold (performance, security, reliability, observability). Load it whenever a task wires the test framework to the stack, touches an environment, a deploy, a pipeline, auth in tests, test IDs, or a performance or security budget, ...testinggoapiVotes: 0GitHub stars: 26
Business E2e ContextAHow people actually use the system under test end to end: the personas, the user journeys first (entry point, steps, branches, where money or data changes hands, where it can fail), then the feature catalog those journeys cross and the flows that span several features. Load it whenever a task touches an E2E or UI test, a user flow, a smoke or regression scope, an exploratory session, a story's place in a bigger journey, or asks what a user can do in the product, even when nobody says 'feature...testinggoapiVotes: 0GitHub stars: 26
Business Domain ContextAThe vocabulary and the business of the system under test: what the product is for, who pays and why, and what every domain term means (the business meaning, the label the UI shows, the identifier the code uses, how it relates to other terms). Load it whenever a task names, labels or explains a domain concept: writing or refining acceptance criteria, authoring an ATP, naming a test case or a test file, filing a bug in business language, or asking what a term means or why a feature exists, even...testinggoawsVotes: 0GitHub stars: 26
Business Data ContextAWhat the system under test IS at the data level: business entities and why they exist, their relationships, state machines, automatic processes (DB triggers, cron jobs, webhooks), external integrations and the business flows that move data between them. Load it whenever a task touches the database, data validation, a SQL query, test data setup, an entity's lifecycle or status transitions, a trigger or a background job, or asks how the product works under the hood, even when nobody says 'data ...testinggosqlVotes: 0GitHub stars: 26
Business Api ContextAWhat the API of the system under test MEANS to the business: every endpoint group, who calls it and why, what it changes, which auth level and role it needs, the business flows that cross several endpoints, error semantics and the external integrations behind them. Load it whenever a task touches an API test, a request or response, an auth or permission question, a status code that looks wrong, contract coverage, or asks which endpoint does what, even when nobody says 'API map'. Reads its map...testinggotestingVotes: 0GitHub stars: 26
Fix Security IssueAImplement a fix for a reviewed security issue. Takes a directly requested issue number or scans for issues labeled `topic:security` and `agent:implementation-requested`. Reads the security review from the issue comments and implements the remediation plan. Trigger keywords - fix security issue, remediate security, implement security fix, patch vulnerability.testingpythonrustVotes: 0GitHub stars: 3
Build From IssueAGiven a GitHub issue number, plan and implement the work described in the issue. Supports direct user requests and unattended queue processing through the `agent:*` workflow labels. Includes tests, documentation updates, and PR creation. Trigger keywords - build from issue, implement issue, work on issue, build issue, start issue.testingpythonrustVotes: 0GitHub stars: 3
Node SmithABuilds exactly one weft node end to end, unsupervised. Dispatched by Tangle with a typed contract (one job, exact ports); researches the real API documentation when the node wraps a service, writes the node and extensive tests in the project's nodes/ folder, and proves it by running weft test-node on the local tiers (basic and fake, never live) until green, then reports with evidence.testingpythonrustVotes: 0GitHub stars: 1,992
Node SmithABuilds exactly one weft node end to end, unsupervised. Dispatched by Tangle with a typed contract (one job, exact ports); researches the real API documentation when the node wraps a service, writes the node and extensive tests in the project's nodes/ folder, and proves it by running weft test-node on the local tiers (basic and fake, never live) until green, then reports with evidence.testingpythonrustVotes: 0GitHub stars: 1,992
Mode CodeACode mode: rules for writing and refactoring code. Style (DRY, SYNC markers, naming), no fallbacks fail loudly, tooling, testing pyramid. Load when switching to [code mode], before writing or editing code, or when fixing review findings.testingpythonrustVotes: 0GitHub stars: 1,992
Mode CodeACode mode: rules for writing and refactoring code. Style (DRY, SYNC markers, naming), no fallbacks fail loudly, tooling, testing pyramid. Load when switching to [code mode], before writing or editing code, or when fixing review findings.testingpythonrustVotes: 0GitHub stars: 1,992
Mode ConvergenceAConvergence mode: synthesize scattered thoughts into coherent structure, extract core insights, output actionable next steps. Load when switching to [convergence mode] or when a rambling discussion needs pulling together.testingnodeVotes: 0GitHub stars: 1,992
Mode CodeACode mode: rules for writing and refactoring code. Style (DRY, SYNC markers, naming), no fallbacks fail loudly, tooling, testing pyramid. Load when switching to [code mode], before writing or editing code, or when fixing review findings.testingpythonrustVotes: 0GitHub stars: 1,992
Mode BabbleABabble mode: stream of consciousness, no structure, half-thoughts and dead ends, thinking out loud. Load when switching to [babble mode] or when early exploration should run unstructured before convergence.testingVotes: 0GitHub stars: 1,992
Flow 4 ReviewAOne wide-net review round over the whole uncommitted diff, then clean reshape fixestestinggonodeVotes: 0GitHub stars: 1,992
Openspec OnboardAGuided 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".testingtypescriptgoVotes: 0GitHub stars: 2