uinaf/verify
Verify your own completed code changes using the repo's existing infrastructure and an independent evaluator context. Use after implementing a change when you need to run unit or integration tests, check build or lint gates, prove the real surface works with evidence, and challenge the changed code for clarity, deduplication, and maintainability. Do not use when the repo is not verifiable yet or when reviewing someone else's code.
93
94%
Does it follow best practices?
Impact
92%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
96%
2%Calculator Library Verification
Guardrails run first
93%
93%
Test output recorded
100%
100%
Failure path exercised
100%
100%
Verdict field present
100%
100%
Change Verified section
100%
100%
Surfaces Exercised section
100%
100%
Self-Corrections section
100%
100%
Exact Evidence section
100%
100%
Recommended Follow-up section
100%
100%
Compact verification footer
62%
87%
Error actionability assessed
75%
75%
No unverified claims
100%
100%
90%
-2%User API Verification
Server started and queried
80%
66%
Real HTTP client used
100%
100%
Actual response captured
100%
100%
Error/failure path exercised
100%
100%
Exact surfaces named
100%
100%
Exact commands recorded
100%
100%
Success kept terse
87%
87%
Finding tied to impact
100%
100%
Valid verdict
100%
100%
Compact verification footer
50%
50%
90%
3%Blocked Verification Handoff
Blocked verdict
100%
100%
Commands attempted
91%
100%
Missing infra evidence
91%
100%
No static proof substitution
92%
100%
Readiness gaps listed
100%
100%
Readiness follow-up
92%
100%
Surfaces not exercised honestly
90%
100%
No invented tests
50%
50%
Compact blocked footer
50%
37%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6