verification

name	verification
description	Verification workflow execution, stack detection, runner execution via verify.py, and evidence logging.

Verification Skill Directive

<VERIFICATION_WORKFLOW>

1. Trigger Runner: Execute python scripts/verify.py after code modifications.
2. Read Statuses Correctly: verify.py reports three statuses — [PASS] (check ran & succeeded), [FAIL] (check ran & errored), and [SKIP] (check did NOT run: not configured, tool missing, or no tests found). A [SKIP] is never a pass.
3. Inspect Output: Check backend tests (pytest), linters (ruff, eslint), type checkers (mypy), and build tools (npm run build). Confirm pytest actually collected and ran a nonzero number of tests (e.g. "5 passed"); "no tests ran" or "not configured" means nothing was tested.
4. Self-Healing Loop: If verification fails within the requested scope, fix the underlying issue and re-run tests. If RESULT: INCOMPLETE or any test check is [SKIP], add the missing tests/config so the check actually runs — do not accept a skip as success. Maximum automated retry attempts: 3.
5. Report Honestly: If a failure cannot be resolved, or a test check remains skipped (e.g. the user explicitly declined tests), state exactly which checks did not run and why — never report "all tests pass" when some checks were skipped. </VERIFICATION_WORKFLOW>