verifier

Verifies code readiness before merge with tiered checks and structured READY, BLOCKED, or UNVERIFIED verdicts.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill verifier-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verifier
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/.opencode/skills/verifier
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill verifier-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need an objective, read-only quality gate before merging code. This Skill inspects changed files against contracts, types, tests, security baselines, and schema alignment, then issues an evidence-backed verdict so nothing ships unverified. ## Core Features & Use Cases - Tiered Verification: Choose Lite (quick fixes, ≤2 files), Standard (route contracts, schema alignment, security baseline), or Full (threat model, security headers, npm audit, runtime proof) depending on the Work Block's risk. - Structured Verdicts: Outputs a JSON verdict of READY, BLOCKED, or UNVERIFIED with per-check PASS/FAIL status, evidence, blockers with file and line references, and non-blocking warnings. - Read-Only Safety: Runs git diff, tests, curl, and security scans without editing production code, committing, or accessing secrets. - Use Case: Before merging an authentication change, run a Full-tier verification to confirm route contracts, run npm audit, check security headers, and receive a BLOCKED verdict with exact file and line evidence if anything fails. ## Quick Start Ask the agent to verify the current Work Block at standard tier and return a READY, BLOCKED, or UNVERIFIED verdict with evidence.

Frequently Asked Questions about verifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code is ready to merge before shipping?▼

Run the verifier at the appropriate tier: Lite for quick fixes, Standard for most work blocks, or Full for security and deployment changes. It checks contracts, types, tests, and security scans, then issues a READY, BLOCKED, or UNVERIFIED verdict with evidence.

What is the difference between Lite, Standard, and Full verification tiers?▼

Lite covers quick fixes of two files or fewer, checking that changes match the task and builds pass. Standard adds route contracts, schema alignment, and a security baseline. Full adds threat modeling, security headers, npm audit, and runtime proof.

Can the verifier modify code to fix issues it finds?▼

No. The verifier is strictly read-only for production code. It can run tests, git commands, curl, and security scans, and write verification artifacts to an approved path, but it cannot edit source, commit, push, or deploy.

What does a BLOCKED verdict mean and how is it reported?▼

A BLOCKED verdict stops the pipeline and must link to a specific failed check with evidence. The output includes blockers with the check name, file, line number, and suggested fix, plus any non-blocking warnings.

When does the verifier return UNVERIFIED instead of READY or BLOCKED?▼

UNVERIFIED is issued when checks cannot be completed, such as missing access or unavailable tooling. It requires an obstacle report describing what was tried and what is needed to finish verification.