All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 31,095
- 1,296
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,049–3,072 of 31,095 skills
- Lemon SqueezyRead Lemon Squeezy revenue: list orders, subscriptions, customers, products; create checkout links. Trigger phrases: lemon squeezy, store orders, revenue, checkout link.Votes: 0GitHub stars: 18
- Provenmap IntegrationIntegrates with the Claude Code Plugin API to push architecture data for visualization on ProvenMap workboards. Use when user asks to "sync to ProvenMap", "push architecture to portal", "configure API", "connect to portal", "upload nodes", or "sync edges". Provides API patterns, authentication, and sync protocols.Votes: 0GitHub stars: 3
- Onboarding AuditAct as a brand-new user of a product and audit its first-run onboarding end to end — sign up with a real email, drive the web app / desktop app / CLI, log every dead end, unexplained error, and undocumented prerequisite, then write a severity-ranked friction report with concrete fixes. Use when asked to "test onboarding", "sign up as a new user", "dogfood the first-run experience", "onboarding QA/audit", or to reproduce a new-user journey and report the friction.Votes: 0GitHub stars: 4
- Generate E2e TestGenerate Playwright E2E tests from user stories or manual workflows; explore flow interactively before writing code.Votes: 0GitHub stars: 4
- Colin Feature ExportCreate an implementation guide for a feature in this repo so you can port it to another repoVotes: 0GitHub stars: 4
- Front DoorWalk a repo's front door as a brand-new user would and report whether they can actually get from clone to working — not just whether the docs exist. Use whenever the user asks to audit, review, or critique a repo's onboarding, installation, setup, getting-started, or quickstart experience; asks "can a new user install this," "is the setup too hard," "why is onboarding so painful," "are there too many READMEs," "which doc is the source of truth," "did we leak an API key," or wants install scri...Votes: 0GitHub stars: 5
- Ci DoctorDiagnose CI health and, when needed, benchmark a config change side by side — without re-deriving either from scratch each time. Use when the operator asks "why is CI slow", "diagnose our CI", "is our CI healthy", "what's the bottleneck", or wants to compare wall-clock across two or more `runs-on` (or other config) variants — e.g. GitHub-hosted vs. a paid runner vendor, or a small vs. large runner tier. Not for writing new workflows from scratch, not for non-GitHub-Actions CI systems, not for...Votes: 0GitHub stars: 5
- Marathon CleanupAudit active PDDA marathon plans and bundles, reconcile every lane against canonical project docs, frontmatter and status tables, GitHub issue and PR state, landed commits, tests, and CHANGELOG evidence, then archive only verified-complete task docs and fully complete marathons. Use when asked to clean up, reconcile, retire, archive, or sweep completed marathon files under PROJECT/2-WORKING, especially after marathon lanes merge. Defaults to report-only and requires explicit confirmation befo...Votes: 0GitHub stars: 5
- HonestProduce an honest, defensible ground-truth read of the current repo — how mature the codebase really is, how far along each feature actually is, and what can be safely claimed about it externally. Reads CHANGELOG, architecture/technical docs, and recent git history; never modifies the repo. Offers an Express (10–15 min) or Deep (30–40 min) scan. Trigger when the user says "baseline", "where do we actually stand", "what's the real state of this repo", "honest assessment of the codebase", "matu...Votes: 0GitHub stars: 5
- WorkhorseEnd-to-end disciplined problem resolution ladder: triages complex multi-task or wall-of-text intake into an atomic priority queue, establishes ground truth via /debug-mantra, engineers the leanest safe solution via /ponytail (reusing and extending existing subsystems with zero code sprawl), enforces AGENTS.md, SOP.md, and GUIDING PRINCIPLES governance, checks cross-repo CHANGELOG cohesion, stress-tests the plan via /consult with Codex and Agy, runs bounded /recon on ambiguous stateful targets...Votes: 0GitHub stars: 5
- ExpressHotfix fast lane (GH-267/GH-516) for an explicit /express, "express this hotfix", or "express GH-N" request. Carries a critical, risk-bounded fix, registered existing covering suite, releases-ledger updates, born-complete PDDA doc, CHANGELOG, landing, and reconciliation in one operator-authorized motion. Requires a task clone branched from origin/development (carrying <= 2 local commits) with the canonical pre-push gate installed, authenticated gh, and the root releases ledger. The driver com...Votes: 0GitHub stars: 5
- 3 COMPLETED- One preparation entry point - Reuse existing planner and marathon runner - Keep explicit fire gateVotes: 0GitHub stars: 5
- 3 COMPLETED| What was just completed | What's next | |---|---| | Issue #436 created and registered. Compliance with `WORKTREE-SAFETY.md` verified across all 6 phases. | Author `skills/merge-cleanup/SKILL.md` and helper scripts (`merge_cleanup.py`, `scan_clones.py`, `toposort_prs.py`). Register in RELEASES DB. Cut fresh full clone, run test suite, QA consult with Qwen 3.8 max, open PR targeting `development`, and tear down clone. |Votes: 0GitHub stars: 5
- Unit TestingUse when writing unit tests for a function or module, mocking external dependencies, practising TDD on new business logic, or enforcing a coverage target across a codebase in Python, TypeScript, or Go.Votes: 0GitHub stars: 189
- Test StrategyUse when choosing a testing model for a new project, auditing a test suite that is slow or provides low confidence, setting coverage targets, or writing a QA test plan for a release.Votes: 0GitHub stars: 189
- Solution TestingUse when writing Playwright E2E tests for critical user journeys, setting up post-deployment smoke tests, debugging flaky browser automation, or implementing BDD feature files with Gherkin.Votes: 0GitHub stars: 189
- Smoke TestingUse when verifying a fresh deployment, gating a CI pipeline before full test runs, checking that core user flows are reachable after a release, or building a minimal health-check suite for a new service.Votes: 0GitHub stars: 189
- Requirements PlanningUse when writing a PRD, drafting user stories with acceptance criteria, breaking an epic into sprint-sized vertical slices, story pointing in planning poker, or defining a team's Definition of Done.Votes: 0GitHub stars: 189
- Feature FlagsUse when adding feature flag support to a service, designing a percentage-based rollout, setting up A/B experiments or multivariate tests, choosing between LaunchDarkly, Unleash, and OpenFeature, writing tests for flag-gated code, or managing flag lifecycle and cleanup.Votes: 0GitHub stars: 189
- QaTest a ticket, feature or bug end to end; resume a QA handoff or plan exploratory testing. Accepts tracker IDs and free text. Does not implement unrelated product features.Votes: 0GitHub stars: 2
- Qa WorkflowInternal QA execution procedure. Load through qa for test planning, execution and evidence; not a separate ticket entry point.Votes: 0GitHub stars: 2
- Qa WebAuthor, execute, diagnose and maintain browser QA using observed UI semantics and business outcomes. Use for web journeys, browser state, interaction and relevant accessibility checks.Votes: 0GitHub stars: 2
- Qa SecurityDesign and execute a bounded security QA slice when access control, sensitive data or another identified security risk is in scope. Apply alongside the affected API, web or mobile skill.Votes: 0GitHub stars: 2
- Qa PerformanceAuthor and execute bounded performance checks with an explicit workload, baseline, thresholds and diagnosis. Apply when latency, throughput, capacity or resource regressions are in scope.Votes: 0GitHub stars: 2