qa-skills-setup

QA Skills setup

This skill installs a runtime, not skills of its own. The eight QA skills — qa-tester, requirement-analyzer, testcase-designer, test-data-manager, browser-test-executor, evidence-collector, bug-reporter, qa-report-generator — are written into the project by qa-skill skills install, checksummed, and bound to the exact runtime binary that wrote them (ADR-0011). This plugin carries no copy of them: a second copy could not be checked by qa-skill skills verify and would drift from the canonical bundle silently.

Run the four steps below in order. Stop at the first one that does not succeed and report what it said — do not work around a refusal, and do not continue to the next step on a non-zero exit.

1. Resolve the runtime

In this exact order: ./node_modules/.bin/qa-skill, then qa-skill on PATH.

QA_SKILL="${PWD}/node_modules/.bin/qa-skill"; [ -x "$QA_SKILL" ] || QA_SKILL="$(command -v qa-skill)" || exit 1

PowerShell:

$QaSkill = Join-Path $PWD "node_modules/.bin/qa-skill.cmd"
if (-not (Test-Path $QaSkill)) { $QaSkill = (Get-Command qa-skill -ErrorAction Stop).Source }

Never use npx against a remote registry, a globally cached binary of unknown origin, or any substitute runtime. The QA Runtime's guarantees rest on the caller having reviewed the exact binary that executes the run.

If neither path resolves, stop and give the user this setup, then wait — do not install packages on their behalf:

npm install --save-dev @gwinnguyen/qa-skills
npx playwright install chromium

Node.js 22 or 24 is required. Chromium must be installed at setup time; QA execution never downloads a browser or a package implicitly.

2. Verify the runtime version range

"$QA_SKILL" runtime verify --range ">=1.0.0 <2.0.0"

Prints JSON with executable, version, range, compatible. If compatible is false, the installed package does not satisfy the v1 contract — report the printed version and stop. Do not widen the range to make it pass.