QA Check, Execute Test Cases

Shell commands are not pre-approved by this skill. Use an exposed execution tool under the runtime's existing permissions for the authorized command and CWD. Reuse applicable authorization; request native approval only when required. Keep the stricter case/production approvals below. Unavailable or denied commands remain blockers/not_run in delegated runs too. Never broaden permissions, use another path to bypass a denial, or report an unexecuted check as passed.

Shared project skill-context

Before mode routing or work, read existing files relative to the current project root in this order (reuse them if already loaded):

1. .ai-factory/skill-context/global-skill-context.md, all bundled skills.
2. .ai-factory/skill-context/aif-qa-check/SKILL.md, this skill.

Missing files are skipped; an existing unreadable file stops dependent work with its path. Precedence: individual > build (when applicable) > global > skill defaults; retain non-conflicting instructions and check all outputs against the effective rules. These layers customize workflow; they do not replace the project's rules/architecture hierarchy or relax explicit requirements, ownership, scope, safety/privacy, validation, or approval boundaries. Report conflicts with those boundaries instead of overriding them. global is a project-local layer, not home-directory configuration. Custom/extension skills do not automatically use it.

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 runs
• agent-history.md, append-only reusable learnings extracted from prior runs, not a per-run audit log