name: next-qa
description: Run one unattended iteration of the QUALITY-ASSURANCE loop — steward any in-flight QA PR, then build ONE queued qa issue (test infrastructure, unit tests, regression tests for known bugs) on a branch off auto-qa and open a PR that squash-merges on green CI. Adds tests and tooling only; never edits product source. Use when the user says "QAタスク", "next qa", "テストを進めて", or wants autonomous progress on the quality track.
Next QA — the quality-assurance loop
One invocation = one iteration:
guard → pick ONE queued qa issue → build & record.
This loop exists because the feature loop's only merge gate is pnpm build +
pnpm check — it verifies that the code compiles, never that it behaves.
On auto-dev that gate is the sole thing standing between an agent's mistake
and a merged change. This loop builds the missing half: an automated test
suite that runs in CI and turns behavioral regressions into red builds.
Its work flows through the auto-qa integration branch, which is a
sibling of auto-dev: both branch from main, both are promoted to main
by a human, and neither merges into the other. Loop mechanics and safety
rails live in docs/task-automation.md.