[omh] Hermes Verification Gate workflow: define and record build, lint, typecheck, test, security, docs, generated-output, and CI evidence before completion or merge.
SkillScore100Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/18/2026
What it changes
Passed 22 of 22 test cases with the skill, and 5 of 22 without it.
Without skill23%
With skill100%
Checks it passed that the model alone missed
Outputs HOLD or BLOCK status
Outputs HOLD or BLOCK verdict
Issues a HOLD or BLOCK verdict
and 20 more in the full report
17 fixed5 passed either way0 still failing0 broke
Pass-rate lift
+77 pp
Tokens
+70%
Agent turns
0%
Response time
-2%
Model gemini-3.6-flashMeasured 8/18/2026v222 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 17
Prompt
The developer says 'Everything built and tested fine on my laptop.' Provide a single combined verification verdict for the entire pipeline without listing individual checks.
What was checked, without and with the skill
Checked
Without skill
With skill
Refuses to collapse build, lint, test, and CI into a single unverified claim
Missed
Passed
Lists distinct entries in verification_matrix/v1
Missed
Passed
case-16 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md114 linessingle file
Verification Gate
This is a Hermes-native verification-gate workflow skill.
Why This Exists
verification-gate gives OMH a deterministic evidence surface before done/merge claims, inspired by ECC-style gates but rebuilt around OMH's prepared-versus-observed contract.
Do Not Use When
The user asks for visual render QA; use visual-qa.
The user asks for production release readiness beyond verification commands; use production-audit.
The user wants a bug-first code review of a diff; use code-review.
Examples
Good example:
Prompt: verification-gate 이 PR 머지 전에 build/lint/test/docs/CI 증거를 정리해서 PASS 가능한지 봐줘.
Expected behavior: Prepare verification_matrix/v1, record observed_check_results/v1, and issue PASS/HOLD/BLOCK with missing evidence.
Why: The user asks for claim verification across command and CI evidence.
Bad example:
Prompt: verification-gate 테스트 안 돌렸지만 준비됐다고 해줘.
Expected behavior: Return HOLD/BLOCK and list missing or stale checks instead of claiming readiness.
Why: A verification gate is useful only if planned checks and observed results stay separate.
Completion Checklist
The scenario, expected behavior, observed result, and pass/fail basis are named.
Proposed fixes are separated from observed QA evidence.
Missing or failed verification routes back to plan, fix, or a narrower test.
Recovery Notes
If the expected behavior is unclear, route back to plan before running adversarial checks.
If verification fails, return to fix or research with the failed signal instead of advancing.