Skip to content
Skills Library
Programming · Testing

qa

/qa

One-prompt QA loop. Runs the qa-tester agent on the current project, dispatches coder agents per finding with the model matched to severity (Blocker→fable, Major→opus, Minor/Polish→sonnet), re-verifies with qa-tester, and repeats until clean or the round cap. Keeps the qa-board sidebar updated. Use when the user says "/qa", "QA this app", "run the QA team", "test and fix", or "find and fix UX issues".

Repository
QA-master ↗
Licence
MIT
Last repository change
02.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

One-prompt QA loop. Runs the qa-tester agent on the current project, dispatches coder agents per finding with the model matched to severity (Blocker→fable, Major→opus, Minor/Polish→sonnet), re-verifies with qa-tester, and repeats until clean or the round cap. Keeps the qa-board sidebar updated. Use when the user says "/qa", "QA this app", "run the QA team", "test and fix", or "find and fix UX issues".

Triggers from the description

QA this apprun the QA teamtest and fixfind and fix UX issues
Original author description

One-prompt QA loop. Runs the qa-tester agent on the current project, dispatches coder agents per finding with the model matched to severity (Blocker→fable, Major→opus, Minor/Polish→sonnet), re-verifies with qa-tester, and repeats until clean or the round cap. Keeps the qa-board sidebar updated. Use when the user says "/qa", "QA this app", "run the QA team", "test and fix", or "find and fix UX issues".

How it works

  1. Arguments
  2. Board
  3. Loop
  4. Rules
Original SKILL.md headings · 68 lines, 780 words
SKILL.md preview
---
name: qa
description: One-prompt QA loop. Runs the qa-tester agent on the current project, dispatches coder agents per finding with the model matched to severity (Blocker→fable, Major→opus, Minor/Polish→sonnet), re-verifies with qa-tester, and repeats until clean or the round cap. Keeps the qa-board sidebar updated. Use when the user says "/qa", "QA this app", "run the QA team", "test and fix", or "find and fix UX issues".
---

# /qa — test, fix, verify, repeat

You are the orchestrator. qa-tester finds, coders fix, qa-tester verifies. You never fix anything yourself.

## Arguments

`/qa [url | app-id] [chrome | ios | android] [device NAME] [verify ID,ID] [rounds N] [polish] [no-fix] [journeys "a, b"]`

- `url`: target. Omitted → qa-tester detects dev servers. With `ios`/`android`, an app id (bundle id / package); omitted → qa-tester reads it from `app.json`.
- `chrome`: use Claude in Chrome instead of Playwright (logged-in sessions).
- `ios` / `android`: drive the installed app on the booted iOS Simulator / running Android emulator instead of a browser. Give both to walk both platforms in one run.
- `device NAME`: a specific simulator name or UDID, or AVD name or adb serial. Default: whatever is already booted.
- `verify ID,...`: skip exploring; verify those IDs from the latest report, then fix what is still open.
- `rounds N`: max fix+verify rounds. Default 2.
- `polish`: also fix Polish findings. Default: Blocker, Major, Minor only.
- `no-fix`: run qa-tester and show the board, do not dispatch coders.
- `journeys`: limit qa-tester to these flows.
- `no-board`: run without the sidebar.

## Board

The sidebar is the `qa-board` plugin. Its tool is `mcp__qa-board__update`; call it at every step below marked **board**.

Before anything else, check the tool list for `mcp__qa-board__update`. If it is missing and `no-board` was not given, reply with exactly this and stop:

> The QA board isn't loaded in this session. Run `/reload-plugins`, then `/qa` again. Or pass `no-board` to run without the sidebar.

With `no-board`, skip every **board** call silently.

## Loop

1. **Start.** **board**: `{ reset: true, phase: "round 1 · testing" }`.
   Note the repo root (`git rev-parse --show-toplevel` or cwd).

2. **Explore.** Spawn `qa-tester` (subagent_type `qa-tester`) with a prompt containing: the target or "detect dev servers", the driver(s), the device if given, journeys if given, and "mode: explore". Wait for it.
   Parse the dispatch block JSON from its reply. If the reply lacks one, read the report file it names and take the block from there.
   **board**: `{ findings: [ { id, title: <finding heading text after the id>, severity, status: "open", fix_with } ] }`.

3. **Decide.** Drop Polish unless `polish`. If nothing is left, or `no-fix` was given, print the summary and stop.

4. **Fix.** Group open findings by severity. For each group, spawn ONE coder agent, all groups in parallel in a single message:
   - `subagent_type`: `general-purpose`
   - `model`: the group's `fix_with` value (fable, opus, or sonnet)
   - `description`: `fix <severity> QA findings`
   - prompt: repo root, report path, the full text of each finding in the group (copy the finding sections verbatim from the report), then:
     "Fix the root cause of each finding listed. Grep every caller before editing shared code. Do not touch unrelated code, do not fix findings not listed, do not edit qa-reports/. Run the project's existing test and lint commands if present. Reply with one line per finding ID: what you changed and which files."
   **board** before spawning: `{ phase: "round N · fixing", set: [ { id, status: "fixing", agent: "<model>" } ... ] }`.
   When each coder returns, **board**: `{ set: [ { id, status: "fixed" } ... ] }`. A coder that says it could not fix an ID → `status: "failed"`.

5. **Verify.** **board**: `{ phase: "round N · verifying" }`. Spawn `qa-tester` with "mode: verify, verify_ids: <all IDs fixed this round>", same target and driver. From its per-ID results, **board**: `verified` for fixed, `failed` for still open.

6. **Repeat.** If any ID is `failed` and round < N: round += 1, go to step 4 with only the failed IDs. Otherwise stop.

7. **Finish.** **board**: `{ phase: "done · <verified>/<total> verified" }`. Reply with:
   - report path
   - a table: ID, severity, final status, files changed (from the coder replies)
   - what was left open and why
   - one line: "Review the diff and commit when happy." Never commit.

## Rules

- Coder agents get the finding text, not your opinion of the cause. The qa report's "Fix hint" is a hint, label it so.
- Never run two rounds of coders on the same ID with the same model; on a retry, step the model up one (sonnet→opus→fable).
- If qa-tester reports it could not reach the target, stop and say what it needs. Do not guess a URL.
- If qa-tester reports the app is not installed on the device, or Maestro is missing for iOS taps, relay its install or build line verbatim in the summary and continue with whatever it did test.
- Everything in `qa-reports/` is qa-tester's; coders and you do not edit it.

Versions

RepositoryScoreLicence
This page · darevv/QA-master90MIT
anilcancakir/claude-code100MIT
builderio/agent-native100MIT
gethamster/plugin100MIT
paradigmxyz/centaur100MIT
lamngockhuong/aiteamkit100MIT
Everyone-Needs-A-Copilot/claude-copilot100MIT
adobe/skills100Apache-2.0
svyatov/supermatt100MIT

Database snapshot: 13.11.2026 · package version 8682615e4540 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100review-workflow
    Run an iterative code-review loop: a review workflow scores the diff by severity, Claude fixes the issues at the chosen strictness, commits, then re-reviews — looping until the review comes back clean. Configurable at invocation: a model ladder (recommended Sonnet → Opus; also…
  • 100diff-review
    Reviews the changes on the current branch by reading git diff against the base branch, then reports concrete findings grouped by severity (blocker, major, minor, nit) with file:line references and a suggested fix for each. Use when asked to review a branch, a pull request,…
  • 100rein-test
    Use this skill when asked to run tests, before committing, or for Tier 3 releases. Runs the project's real test command by default; --generate dispatches the headless test_engineer Tester (Claude, sonnet) to write tests; --fast runs the Tester on haiku; --vibe triggers the…
  • 100code-review
    Review a diff or pull request against team standards and rank findings by severity (blocker, major, minor, nit) with file, line and a concrete fix. Use when the user asks to review a PR, a branch, a patch, staged changes, or "look over this code" before merge.
  • 100md-tester
    Use when the user invokes /md-tester to manage test spec markdown files, add or update or delete test entries, process ai|feedback annotations, run integration tests, or fix failing tests.
  • 100tester-playbook
    Playbook for working with the tester-squad agent team — which tester agent to use for which job, the standard testing pipelines (requirements review, test planning, feature testing, exploratory, regression, bug report, fix verification, accessibility audit, API testing,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.