aif-qa-check
QA Check — Execute Test Cases
Runs the test-cases.md artifact produced by /aif-qa and records execution status in qa-check.md.
In agent mode, it also maintains reusable cross-QA execution memory under the QA root:
agent-context.md— curated, current, reusable non-sensitive setup facts for future automated QA runsagent-history.md— append-only reusable learnings extracted from prior runs, not a per-run audit log
For browser/UI cases, agent mode saves executable replay scripts under the branch-specific browser-replay/ directory. Later runs execute those scripts first, including scripts for previously passed cases, so fixes are retested and prior behavior gets regression coverage without regenerating browser automation.
The skill is stack-free and agent-free: it does not assume a framework, package manager, browser tool name, or agent runtime. In agent mode, it uses the appropriate available execution surface for each case: live browser automation, CLI commands, project test runners, HTTP/API calls, database-safe read checks, file/document inspection, or other non-destructive automated verification.
Modes
| Argument | Mode | What you do |
|---|---|---|
human |
Human-guided QA | Show exactly one test case, ask the user whether it works, and record their answer |
agent |
Automated-agent QA | Execute test cases through the most appropriate available capability and record observed results |
If no mode is provided, ask the user which mode to run.