!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,qa.level,testing.strict

Automation mode: Resolve modes.automation (project.local.yaml → project.yaml → default collaborative). Every AskUserQuestion call and every file write follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

qa.level and testing.strict (resolved above) decide what this review may call a blocker, the same rules /story-done closes stories by, so a BLOCKING item here is one that would stop /story-done:

• qa.level: minimal waives tests. A Logic, Integration or Config/Data story with no test evidence (for Config/Data, no smoke report) is WAIVED (qa.level: minimal), not MISSING, and raises no BLOCKING item; a test that does exist is still reviewed, but its gaps are ADVISORY. Visual/Feel and UI evidence (the retained screenshots, and the Visual/Feel sign-off) is never waived.
• Gate level per story type: take testing.strict.<type> from the resolved block (Logic→logic, Integration→integration, Visual/Feel→visual, UI→ui, Config/Data→config): true → BLOCKING, false → ADVISORY, unset → a plain-boolean testing.strict: true|false (legacy form) applies to every type; else the Default Gate Level in .claude/docs/coding-standards.md (BLOCKING for Logic, Integration, Visual/Feel and UI; ADVISORY for Config/Data). Every "BLOCKING" below means that story type's gate level.

Test Evidence Review

/smoke-check verifies that test files exist and pass. This skill goes further, it reviews the quality of those tests and evidence documents. A test file that exists and passes may still leave critical behaviour uncovered. A manual evidence doc that exists may lack the sign-offs required for closure.