All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 29,137
- 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 browserBrowse testing & qa skills
Showing 97–120 of 29,137 skills
- Business E2e ContextHow 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...Votes: 0GitHub stars: 26
- Business Domain ContextThe 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...Votes: 0GitHub stars: 26
- Business Data ContextWhat 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 ...Votes: 0GitHub stars: 26
- Business Api ContextWhat 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...Votes: 0GitHub stars: 26
- Fix Security IssueImplement 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.Votes: 0GitHub stars: 3
- Build From IssueGiven 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.Votes: 0GitHub stars: 3
- Node SmithBuilds 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.Votes: 0GitHub stars: 1,992
- Node SmithBuilds 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.Votes: 0GitHub stars: 1,992
- Mode CodeCode 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.Votes: 0GitHub stars: 1,992
- Mode CodeCode 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.Votes: 0GitHub stars: 1,992
- Mode ConvergenceConvergence 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.Votes: 0GitHub stars: 1,992
- Mode CodeCode 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.Votes: 0GitHub stars: 1,992
- Mode BabbleBabble 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.Votes: 0GitHub stars: 1,992
- Flow 4 ReviewOne wide-net review round over the whole uncommitted diff, then clean reshape fixesVotes: 0GitHub stars: 1,992
- 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: 2
- Openspec Archive ChangeArchive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".Votes: 0GitHub stars: 2
- 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: 2
- Openspec Archive ChangeArchive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".Votes: 0GitHub stars: 2
- VerifyVerify ticket completion criteria — use when finishing a ticket,Votes: 0GitHub stars: 19
- TestingHow to write good tests. Use when writing tests, improving testVotes: 0GitHub stars: 19
- RefactorImprove code structure without changing behavior. Use whenVotes: 0GitHub stars: 19
- Cleanup ZombiesKill zombie dev servers and test processes. Use when ports areVotes: 0GitHub stars: 19
- QaUse after code changes, before releases, or when testing features - runs the right level of QA based on what changedVotes: 0GitHub stars: 13
- TestingDraftForge test infrastructure for writing backend unit tests, Playwright E2E tests, and managing test data population. This skill should be used when writing new tests, adding test fixtures, creating populate functions for new features, adding Playwright E2E specs, using login/auth fixtures, creating test users/orgs/leagues/tournaments, or understanding the test data architecture. Covers backend Django tests via Docker, Playwright config (projects, workers, sharding), test auth endpoints tha...Votes: 0GitHub stars: 15