QA skills and agents: test-plan generation, manual test execution with recon and independent evidence review, a curated knowledge bank, bug filing, and promotion of strong scenarios to regression tests.
Plugin qa-flow from marketplace qa-flow in QAMarcos/claude-qa-flow. Commands read from the repo's manifest — 9 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
create-test-plan-scenariosTurn a task/ticket into a structured, professional QA test plan — a checklist of atomic, executable scenarios — and (optionally) post it back to your issue tracker. Use whenever the user asks to "create a test plan", "list test scenarios", "criar cenários de teste", "QA checklist for TICKET-XXXX", o
file-bug-ticketFile a bug (or feature/chore) ticket in your issue tracker via its REST API with a terse, budgeted description, attached screenshot evidence, owner/priority/placement filled in, and a verification GET before reporting done. Use whenever the user asks to "file a bug", "open a ticket", "criar um card"
manual-testExecute exploratory/manual QA against a web app, driven by either a ticket's test plan or a single ad-hoc scenario the user describes. Use whenever the user asks to "run a manual test", "fazer um teste manual", "execute this scenario", "validate this ticket manually", "manual test for TICKET-XXXX",
promote-to-regressionTurn ONE reviewed manual QA run (a throwaway Playwright script + its report and evidence) into a committed regression spec in the project's e2e suite — only if the scenario is strong enough to earn a permanent place, rewritten in the suite's own conventions, proven stable and proven able to fail, an
scan-regression-candidatesSweep a QA scratch root (default `_local/`, where manual-test keeps its throwaway scripts, evidence and logs) and list the few scenarios worth turning into committed regression tests — scored for value and cost, checked against the existing suite, with probes, one-offs and already-covered flows filt
qa-evidence-reviewerIndependently reviews a manual QA run — opens the screenshots, logs and scripts itself, attacks fragile PASS verdicts, finds missing coverage, and classifies each finding with the severity gate. Read-only; dispatched by the manual-test skill with a fresh context, never as a fork of the executor.
qa-test-executorExecutes an already-resolved manual QA plan against a running web app with a throwaway Playwright script, captures evidence, and returns a per-step PASS/FAIL report. Dispatched by the manual-test skill; never writes to the issue tracker and never asks the user questions.
node "${CLAUDE_PLUGIN_ROOT}/scripts/guard-tracker-writes.mjs"
Collection of example skills demonstrating various capabilities including skill creation, MCP building, visual design, algorithmic art, internal communications, web testing, artifact building, Slack GIFs, and theme styling
19 skills
Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification
1 command · 6 agents
Build, preview, and test UI components with Storybook.
7 skills
Agentic QE (external: maintained in proffesor-for-testing/agentic-qe, pinned to v3.15.17): a quality-engineering fleet with 11 QE agents, 9 skills, 9 commands, the agentic-qe MCP server pinned to the plugin version, and the aqe-mod guard that refuses destructive operations on AQE learning data
9 skills · 9 commands · 11 agents · 1 MCP server
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Install the "AAS QA & Test Automation" editorial skill bundle for Claude Code.
14 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.