zereight Verify
Turn vague "it should work" claims into concrete evidence.
Workflow
- Identify the exact behavior that must be proven
- Prefer existing tests first
- If coverage is missing, run narrowest direct verification commands
- If direct automation not enough, describe manual validation steps
- Report only what was actually verified
Verification Order
- Existing tests
- Typecheck / build
- Narrow direct command checks
- Manual or interactive validation
Rules
- Do not say a change is complete without evidence
- If a check fails, include the failure clearly
- If no realistic verification path exists, say so explicitly
- Prefer concise evidence summaries over noisy logs
Output
- What was verified
- Which commands/tests were run
- What passed
- What failed or remains unverified