Testing & QA

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

skills in category: 29,137
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 49–72 of 29,137 skills

CompensationAOffers, compensation framing, and negotiation planning. Use when evaluating offers or raises.testinggodocumentationVotes: 0GitHub stars: 2
Security AuditASecurity guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused security reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts. Not for general code or PR review; use code-review.testingrustgoVotes: 0GitHub stars: 2
Map ModuleACreate, fully refresh, or incrementally maintain a source-verified subsystem architecture map under `.claude/maps/`. Use when the user says "/map-module", "map this module", "map the <subsystem> architecture", asks to document how a subsystem works today, or when project instructions (the Knowledge Loop Conventions in CLAUDE.md) require a targeted refresh after implementation changes invalidate mapped facts. Do not use for ad hoc code explanation, a single-file question, or changes that leave...testingrustgoVotes: 0GitHub stars: 19
ReviewATrusted read-only methodology for independent Omnix code reviewers.testingrustapiVotes: 0GitHub stars: 2
Nix For DevAUse this when setting up Nix for a development project (devShell + package build) and you care about `nix develop` being fast. Covers the zero-inputs flake.nix + npins + default.nix/shell.nix layout, sub-flakes for non-user-facing Nix, and language-specific recommendations.testingtypescriptgoVotes: 0GitHub stars: 11
Nix CiAUse this when setting up CI for a GitHub repository — offers GitHub Actions or Vira depending on the projecttestinggogitVotes: 0GitHub stars: 11
PlansA> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** Add a `qa-report` skill that turns any finished run (`/qa-test`, `/qa-test-fast`, `/qa-verify-fix`, `/qa-regression`, `/qa-smoke`) into **one** brief, char-budgeted tracker comment and **one** human-readable HTML page. Every template lives in one folder, and the f...testinggoshellVotes: 0GitHub stars: 2
Test Tenant ProvisionerAMANUAL-ONLY; never auto-invoke. Provision and verify repeatable test tenants and users in a named NON-PRODUCTION environment for auth, row-level-security (RLS), integration and end-to-end (E2E) runs. Every created row carries a test marker and unmarked rows are never mutated; validate-only mode (the default) reports drift against the persona catalog, apply mode creates or repairs only marked tenants, users and memberships; credentials are referenced by environment-variable NAME only; capabili...testinggotestingVotes: 0GitHub stars: 4
Ci Failure ClassifierBClassify a CI run''s failures and hidden problems from its logs and reports: each failed or suspicious job gets exactly one class (product bug, test bug, missing secret or config, timeout-only, infrastructure, skipped-runtime where a skip hides the real result, or indeterminate), with duration as first-class evidence and timeouts never conflated with regressions; GREEN runs are scanned for hidden runtime markers (console errors, unhandled rejections, unexpected skips, auth failures). Reads lo...testingjavascriptrustVotes: 0GitHub stars: 4
Formulating Atomic Decision QuestionsATurn each fork in an agent into a typed question with a fixed answer space and a written rubric, so a decision model answers and code branches.testinggotestingVotes: 0GitHub stars: 2
Enforcing Deterministic Execution BoundariesAMake code the only path to side effects: gate permissions, validate arguments, run tools, and verify and log real outcomes.testingrustgoVotes: 0GitHub stars: 2
Designing Technical Environments For FocusASet up shared version control, unattended automated tests, frequent integration and protected focus time for developers.testingrustgoVotes: 0GitHub stars: 2
Benchmarking And Observing Agent LoopsAMeasure a full agent loop end to end, run new decision layers in shadow mode, and log versioned decisions so every change can be attributed.testinggotestingVotes: 0GitHub stars: 2
Upgrade DepsAUpgrade a Node repo's dependencies in three rounds (patch → minor → major) using npm-check-updates, respecting the project's release-age cooldown. Researches each update's changelog in parallel, bumps the uneventful ones silently, runs the tests, commits, and surfaces only the packages that need a human decision -- a few at a time, most severe first. Works in monorepos (--workspaces, syncpack). Use when the user runs /upgrade-deps, or asks to "upgrade deps", "bump dependencies", "update packa...testingtypescriptgoVotes: 0GitHub stars: 3
Translate Arabic FinanceATranslate supplied finance analysis to Saudi institutional Arabic (ar-SA), keeping RTL text intact. For Parallax reports, use the analysis skill's lang=. NOT for new analysis or non-finance text.testingpythonshellVotes: 0GitHub stars: 5
JavaAModern Java practices: design, errors, concurrency, security, testing, tooling. Targets Java 21 LTS baseline; Java 25 LTS features called out explicitly. Use when writing or reviewing Java code.testingrustgoVotes: 0GitHub stars: 54
Bible Fts SearchAFull-text search capability for Bible applications with advanced features like Porter stemming, relevance ranking, and search result highlighting. Integrates with SQLite FTS5 for high-performance text search across Bible verses, notes, bookmarks, and user data.testinggokotlinVotes: 0GitHub stars: 2
VerifyAVerify a requested change or claim with fail-first evidence, targeted checks, live output, and exit codes. Use for 'çalışıyor mu', 'testleri çalıştır', 'doğrula', 'kanıtla', and before declaring a bugfix, feature, refactor, or API change complete. Not for silently repairing a failing project or claiming visual, security, or production behavior from an unrelated unit test.testinggobashVotes: 0GitHub stars: 2
Durable ObjectsACreate and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.testingtypescriptshellVotes: 0GitHub stars: 2
Workflow Integration TestA[Workflow] Use when writing integration tests spec-first, converting test specs into test code, adding coverage to untested code, or driving failing integration tests to green. Flag: --mode={write|green}.testinggotestingVotes: 0GitHub stars: 3
Workflow Integration TestA[Workflow] Use when writing integration tests spec-first, converting test specs into test code, adding coverage to untested code, or driving failing integration tests to green. Flag: --mode={write|green}.testinggotestingVotes: 0GitHub stars: 3
Praxis ShipAUse when the code of the active ticket is written (or a plan with remaining phases exists) and the user wants it taken to a pull request — "/praxis-ship", "on livre", "commit + PR", "fais la QA et ouvre la PR", or a goal of the form "implémente les phases, /praxis-review, QA, commit, PR". Requires praxis tracking (.current). Do NOT use for the initial plan (/praxis-spec), for triage (/praxis-triage) or for a bug fix without tracking (/praxis-fix).testinggobashVotes: 0GitHub stars: 3
Praxis Review PrAReview a GitHub PR and produce GitHub-ready review comments with file, line, and markdown. Handles re-reviews after fixes and groups of related PRs. Use when the user asks to review a PR by number, URL, or chat link ("review pr 123", "review-pr #456", "fais une review de la pr 789", "la pr X a été corrigée, refais une review").testinggobashVotes: 0GitHub stars: 3
Praxis QaAUse when a change must be checked in a real browser against the ticket and the design — "qa local", "qa <env>", "teste en local", "vérifie sur <env>", after a deploy to a shared environment, or as the QA stage of /praxis-ship. Do NOT use for unit tests, nor to write E2E tests.testingnodetestingVotes: 0GitHub stars: 3