All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 31,457
- 1,311
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 4,297–4,320 of 31,457 skills
- VerifyVerify code changes work by running them. Proves through execution, notVotes: 0GitHub stars: 3
- TestTest generation and test running command. Creates and executes testsVotes: 0GitHub stars: 3
- Systematic DebuggingSource: obra/superpowersVotes: 0GitHub stars: 3
- Nodejs Best PracticesPrinciples and decision-making for Node.js development in 2025.Votes: 0GitHub stars: 3
- DebugDebugging command. Activates DEBUG mode for systematic problem investigation.Votes: 0GitHub stars: 3
- Webapp TestingWeb application testing principles. E2E, Playwright, deep audit strategies.Votes: 0GitHub stars: 3
- Testing PatternsTesting patterns and principles. Unit, integration, mocking strategies.Votes: 0GitHub stars: 3
- Systematic Debugging4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.Votes: 0GitHub stars: 3
- QaRun quokka's real-device E2E layer (QA strategy layer 5): drive the real qk binary against connected iPhone/Android devices through tmux, apply deterministic verifiers, and write a report. Use when the user asks to "run /qa", "run the device QA suite", "test against the real device", or before a release. Optionally finishes with an advisory exploratory UX pass (layer 6).Votes: 0GitHub stars: 101
- Relentless TesterAutonomous QA tester that systematically tests every rdst command via tmux harness, applies a quality rubric, and files bugs in beadsVotes: 0GitHub stars: 16
- Create PlanCreate concise, actionable plans for coding tasks. Scope work, identify dependencies, and deliver atomic, ordered steps from discovery through validation and rollout.Votes: 0GitHub stars: 16
- Codebase MigrateCoordinate large-scale codebase migrations and multi-file refactors across hundreds of files. Manage framework upgrades, API renames, and config rewrites using batched PRs, issue tracking, and CI verification.Votes: 0GitHub stars: 16
- GuidesThis guide provides specific test cases for manually testing the UV skill to ensure it works correctly with Claude Code.Votes: 0GitHub stars: 106
- Testing Safe ProtocolSafe testing practices to prevent real-world side-effects. TRIGGER when user asks to "run tests", "test this", "write tests", "debug", "mock", "fixture", "integration test", "unit test", or when testing code that touches network, database, filesystem, or external services. Use BEFORE executing any test that could affect production systems.Votes: 0GitHub stars: 106
- Interactive TestUse this skill before testing interactive applications (GUI/TUI).Votes: 0GitHub stars: 106
- Harness WorkUse when implementing, executing, or running Plans.md tasks — single task, parallel workers, or full team/breezing run. Accepts specific task numbers or ranges. Do NOT load for: planning, review, release, or setup.Votes: 0GitHub stars: 34
- BreezingUse when running the full team/breezing flow end-to-end — all tasks with parallel workers. Do NOT load for: single-task implementation, planning, review, release, or setup.Votes: 0GitHub stars: 34
- EnRecord & Replay lets Codex learn a user-demonstrated macOS workflow and turn it into a reusable skill. Use it when the user asks you to watch them perform a task, record a workflow, or create or refine a skill from their demonstration.Votes: 0GitHub stars: 189
- Swift CodingSwift coding conventions and project structure. Use when writing or modifying Swift files.Votes: 0GitHub stars: 29
- Racket CodingRacket coding conventions. Use when writing or modifying Racket (.rkt) files.Votes: 0GitHub stars: 29
- Github TasksTrack work as GitHub issues in this monorepo — create epics + child/sub-issues, label them consistently by package/app, and tie them into the commit workflow. Use when planning a feature, breaking work into tasks, or asked to "track this in GitHub", "make issues", "set up tracking".Votes: 0GitHub stars: 10
- Crouton Validation RealityHow to actually run every kind of test in nuxt-crouton (unit/e2e/typecheck/lint, verified commands) plus the HONEST coverage picture — which packages have real tests vs zero, the dormant skipped/todo cases behind three mocking walls, and what CI truly gates vs what CLAUDE.md claims. Use when asked "how do I run the tests", "is X covered by tests", "what does CI actually check", "why is this suite skipped", "where do I add a test", or before trusting a green build as evidence that something wo...Votes: 0GitHub stars: 10
- Crouton Run And OperateDay-to-day operation runbook for nuxt-crouton apps — boot any app/POC locally with auth working, seed and inspect the local database (including the miniflare-vs-.data split that makes seeded data "disappear"), turn on the review overlay / eruda, observe deployed staging (tail, smoke, row counts), and capture screenshots. Use when asked to "run the app", "boot velo/fanfare/a poc locally", "why can't I log in locally", "seed the database", "the seed data doesn't show up", "look at the local db"...Votes: 0GitHub stars: 10
- Crouton Harness ObservabilityHow to MEASURE this repo instead of eyeballing it — interpret the loop-station context-budget trend (history.jsonl, thresholds, the tokenizer-switch gotcha), read a session trace, use the eval ledger (cost-per-success), and pick the right evidence tool (app-shots, smoke-deployed, db-counts, --check modes). Use when asked "is the harness bloating", "how big is CLAUDE.md really", "did this agent run actually succeed", "prove this works", "what evidence do we have", or when tempted to declare a ...Votes: 0GitHub stars: 10