Skip to content
Skills Library
Programming · Automation

qa-setup

/qa-setup

Run /qa-setup once per project to configure the QA Stack. Use it before the first /qa-mode run, when reply language, spawn caps, execution mode, the issue tracker, or the browser driver change. It detects capabilities, writes the config file the router reads, and reports what it found.

Repository
qa-stack ↗
Licence
Apache-2.0
Last repository change
12.11.2026

Assessment and security

100/ 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.
Content35 / 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
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Run /qa-setup once per project to configure the QA Stack. Use it before the first /qa-mode run, when reply language, spawn caps, execution mode, the issue tracker, or the browser driver change. It detects capabilities, writes the config file the router reads, and reports what it found.

Original author description

Run /qa-setup once per project to configure the QA Stack. Use it before the first /qa-mode run, when reply language, spawn caps, execution mode, the issue tracker, or the browser driver change. It detects capabilities, writes the config file the router reads, and reports what it found.

How it works

  1. What to record
  2. Detection
  3. Questions
  4. Reply
Original SKILL.md headings · 65 lines, 420 words
SKILL.md preview
---
name: qa-setup
description: Run /qa-setup once per project to configure the QA Stack. Use it before the first /qa-mode run, when reply language, spawn caps, execution mode, the issue tracker, or the browser driver change. It detects capabilities, writes the config file the router reads, and reports what it found.
license: Apache-2.0
---

# QA setup

One config file, written once, read by every run.

## What to record

Write or update a config file at `qa-stack.config.md` in the repository root.
Record exactly these lines, each as `# key: value`.

- `# reply-language:` one of `en`, `th`, `match`. `match` mirrors the user's
  latest message. Unset means `en`. Artifacts follow `artifact-language`.
- `# artifact-language:` one of `en`, `th`, `match`. The language issues,
  reports, and specs are written in. Unset means `en`. `match` writes the
  artifact in the language of the report that produced it.
- `# max-spawns-per-run:` a number or `none`. The router counts every spawn,
  including retries and reviewers, and stops at the cap to ask.
- `# execution-mode:` one of `solo`, `subagents`, `team`, `auto`. `auto`
  detects on the next run.
- `# issue-tracker:` the tracker identifier when the repository declares
  it unambiguously, otherwise `none`. Never a setup question; qa-file
  resolves it at first file.
- `# browser-driver:` the scripted driver, `playwright` or `none`. See
  detection below.
- `# real-browser-driver:` the real-browser layer for logged-in flows,
  `ego-lite` or `none`. Absent means `none`, never a mid-run install.

## Detection

Run these checks and record the results. Never guess a capability.

1. **Spawn capability.** Does the host expose a subagent or spawn tool? See
   `docs/harness.md` for the name per host. Present means `subagents` or
   `team` is available.
2. **Team capability.** Does the host expose teammates or a task board?
   Present means team mode is available.
3. **Issue tracker.** Never touched at setup. Record `# issue-tracker:`
   only when the repository already declares its tracker unambiguously,
   for example a single tracked remote. Otherwise record `none` silently
   and let qa-file resolve the tracker at first file, not setup. Do not
   check authentication, do not ask about repositories, do not fail on a
   missing tracker CLI.
4. **Browser drivers.** Scripted layer: is Playwright installed? Detect it
   from the project config, for example `playwright.config.*`. Record
   `playwright` or `none`. Real-browser layer: is a real-browser agent
   browser such as ego lite installed on the machine? Record the result;
   absent is fine and the fallback chain applies. Detection details live
   in `../qa-browser/references/drivers.md`.

## Questions

Ask at most one gate question per turn, and only these:

- Reply language, when unset.
- Execution mode, when detection is ambiguous.

Everything else, detect and record. The tracker is never a setup
question.

## Reply

Report what was written, one line per setting, and what was detected but not
configured. Say the config path. A re-run changes settings; it never resets
the ones you did not name.
Files in this package (2)
  • CHANGELOG.md 1 KB
  • SKILL.md 3 KB

Versions

RepositoryScoreLicence
This page · jirayusueb/qa-stack100Apache-2.0
ghassenazzouz/claude-qa-agent100MIT

Database snapshot: 13.11.2026 · package version 99aa85011732 (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

  • 90setup
    One-time project setup for the dev-pipeline plugin. Detects the project's stack and build/test commands, asks a few short questions, and writes dev-pipeline.json in the project root. Use when the user says "set up dev-pipeline", "configure the pipeline", "change which model does…
  • 100react-router-framework-mode
    Build full-stack React applications using React Router's framework mode. Use when configuring routes, working with loaders and actions, handling forms, handling navigation, pending/optimistic UI, error boundaries, or working with react-router.config.ts or other react router conventions.
  • 100setup-issue-loop
    Install issue-loop into a target repository, collect and validate its config, check the tracker, intake, runner, and app-control skill, hand off the two automations, and run the thread-safety test. Use for first install or any config change.
  • 100qa-target-setup
    Interactive setup for a new target application. Navigates to the URL, detects auth requirements, walks through login flow creation, auto-detects scope, and saves target config. Use when user says: "setup target", "add target", "configure app", "new target".
  • 88setup-matt-pocock-skills
    Configure a repo for the engineering skills: set up its issue tracker (GitHub, GitLab, local markdown, or other), triage label vocabulary, and domain doc layout (single-context or multi-context). Run once before first use of other engineering skills. Prompt-driven skill that…
  • 100configure
    Sets up or edits the plugin configuration file interactively. Use on first-time setup, when config is missing, or when the user wants to change settings.

Feedback and reports

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