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. If the repo is not verifiable yet, hand off to `agent-readiness`; if you are reviewing someone else's code, use `review`.
97
100%
Does it follow best practices?
Impact
89%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
77%
7%Auth Token Module Review
any type flagged
100%
100%
Unsafe cast flagged
0%
0%
Non-null assertion flagged
100%
100%
Dead code identified
100%
100%
Duplicate logic identified
100%
100%
Catch-all error flagged
100%
100%
Error classification recommended
100%
70%
Narrating comments flagged
0%
100%
Findings tied to impact
100%
100%
Valid verdict
0%
0%
100%
Calculator Library Verification
Guardrails run first
100%
100%
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%
Code-Shape Findings section
100%
100%
Exact Evidence section
100%
100%
Recommended Follow-up section
100%
100%
Error actionability assessed
100%
100%
No unverified claims
100%
100%
91%
-1%User API Verification
Server started and queried
80%
80%
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
37%
25%
Finding tied to impact
100%
100%
Valid verdict
100%
100%
- Evaluated
- Agent
- Claude
- Model
- Claude Sonnet 4.6