All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 31,128
- 1,297
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,937–3,960 of 31,128 skills
- Orca OrchestrationMulti-session agent orchestration for this repo: one conductor session coordinating a fleet of persistent worker sessions (one per story, per module, per failure cluster) through the Orca runtime, plus the non-Orca fallback where the same launch lines are pasted by hand. Owns the HOW of fleet work — terminals, Runs, Tasks, dispatch, briefs, claims, board cards, liveness, cleanup — while each workflow skill keeps owning the WHAT. Use when the user wants to: orchestrate or parallelize work acro...Votes: 0GitHub stars: 26
- Judgment DayTrigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.Votes: 0GitHub stars: 26
- Jira AdministrationRun bounded Jira administration workflows for project Components or Atlassian instance migration. Use for jira-components, sync Jira components, jira-instance-migration, changed Jira URL, or repoint Jira. Both modes are sealed behind read-first analysis and explicit user approval before any Jira, credential-session, or repository mutation.Votes: 0GitHub stars: 26
- Git Flow MasterEnd-to-end Git operator for any branching strategy. Auto-detects the project's strategy (solo-main, main+integration, enterprise multi-branch, trunk-based, GitFlow, GitHub Flow, GitLab Flow, SDET integration-trunk for chained test-automation suites) from .git config, branches, and the `git_strategy:` block in `.agents/project.yaml`, then adapts every commit, branch, push, PR, conflict-fix, and chained-PR action to that strategy. Use this skill whenever the user wants to: create a branch (`cre...Votes: 0GitHub stars: 26
- Framework DevelopmentFramework evolution mode — evolves the QA boilerplate itself (KATA, fixtures, cli/, scripts/, api/schemas/ pipeline, package.json deps). Self-contained Plan → Code → Verify → Archive pipeline; needs nothing outside the repo (no SDD-* skills). Use when adding new fixture APIs, refactoring KATA base classes, evolving the installer, modifying the OpenAPI sync pipeline, or any change to the framework infrastructure that is NOT per-ticket test writing or manual QA. Triggers on: /framework-developm...Votes: 0GitHub stars: 26
- Agentic Qa OnboardWalks new users through this repo's QA flow — Playwright + KATA + Allure + Xray stack, Jira QA state machine (statuses read from `.agents/jira-workflows.json`, never from memory), the IQL stages by name, /shift-left-testing for pre-sprint AC refinement on backlog Stories, /sprint-testing for in-sprint manual QA, /test-documentation for TMS test cases, /test-automation for KATA-compliant E2E/API tests, /regression-testing for CI suite execution, /framework-development for boilerplate evolution...Votes: 0GitHub stars: 26
- Agentic Qa CoreFoundation skill that hosts shared references cited by other workflow skills (briefing template, dispatch patterns, orchestration doctrine, skill composition strategy). Loaded on demand by any skill that declares `agentic-qa-core` in its Dependencies block. Do NOT use for: adapting KATA tests (use `/test-framework-adaptation`), or onboarding the target project (use `/project-discovery`).Votes: 0GitHub stars: 26
- AcliAtlassian CLI (official `acli` binary) for Jira Cloud, Confluence Cloud, and org admin tasks from the terminal. Use whenever the user wants to create, view, edit, transition, assign, clone, archive, comment on, link, or bulk-operate on Jira work items; list or manage projects, boards, sprints, filters, dashboards, or custom-field definitions; create or update Confluence spaces, pages, or blog posts; activate/deactivate users at the org level; or authenticate to Atlassian from a shell or CI pi...Votes: 0GitHub stars: 26
- Muggle TestChange-driven E2E acceptance testing: detects the user's recent changes (local diff or PR), maps them to affected user flows, and runs real-browser tests on localhost or a preview/staging URL. Invoke it before inspecting anything — what changed and what it affects is its own first step; reading the diff by hand duplicates it. Use when the user wants to test or regression-test their own work — \"make sure I didn't break anything\", \"did my recent commits break any user flows?\", \"test before...Votes: 0GitHub stars: 16
- Muggle Test Feature LocalRun a real-browser end-to-end (E2E) acceptance test against localhost to verify a feature works correctly — signup flows, checkout, form validation, UI interactions, or any user-facing behavior. Launches a browser that executes test steps and captures screenshots. The browser runs under a real identity: each managed login profile owns a live inbox, so magic-link and sign-in-link logins, emailed OTPs, email-based 2FA, verification mail, and password resets are all testable without a mail stub ...Votes: 0GitHub stars: 16
- Optimize DescriptionsOptimize Muggle AI's customer-facing text (MCP tool descriptions, skill descriptions, plugin metadata, hooks) so that AI agents prioritize muggle tools for E2E acceptance testing, UI validation, and browser testing. Internal tool — lives outside the published plugin surface.Votes: 0GitHub stars: 16
- OffstageRun browser, UI and macOS app work without taking over the user's screen. Use before any command that could open a window or steal focus (Playwright, Puppeteer, Cypress, WebDriver, `--headed` or `headless: false` runs, screen or video capture, `xcodebuild`, `xcrun simctl`, XCUITests, iOS/macOS simulators, `open -a`, `osascript`, or launching a built `.app`. offstage decides whether the command is already safe to run in place, needs a Linux container with a virtual display, or needs the macOS ...Votes: 0GitHub stars: 4
- Playwright TestgenUse when preparing a repository for Testgen, discovering Playwright scenarios, turning human-approved scenarios into grounded end-to-end specs, running and repairing a spec produced by that workflow, or explicitly requesting Explorer, Author, or Healer standalone.Votes: 0GitHub stars: 2
- 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
- Webapp TestingDiscover and test everything. Leave no route untested.Votes: 0GitHub stars: 3
- 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