verifier

Evaluates code changes against acceptance criteria using build, test, and diff evidence.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/benediktms/overmind --skill verifier-benediktms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verifier
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/verifier
Command: npx skills add https://github.com/benediktms/overmind --skill verifier-benediktms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates completed work against acceptance criteria and returns evidence-backed pass/fail verdicts. Use when implementation is complete and needs an acceptance decision, a relay or swarm flow requires a formal quality gate, or scope compliance must be validated before merge. Does not implement or redesign. Not for incomplete work, exploratory design, or tasks needing bug diagnosis.

Core Features & Use Cases

  • Validate acceptance criteria, run checks, and deliver a clear pass/fail verdict based on concrete evidence.
  • Tie every verdict to concrete outputs from builds, tests, and diffs to ensure traceability.
  • Suitable for pre-merge gates, relay or swarm workflows, and scoped quality validation across multi-file changes.

Quick Start

Run the verifier on the current changes to obtain an evidence-backed pass/fail verdict.

Frequently Asked Questions about verifier

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

FAQPage Schema
How do I validate code changes against acceptance criteria before a merge?

An evidence-backed quality gate evaluates completed work against acceptance criteria by aggregating build outputs, test results, and change diffs. It returns a formal pass or fail verdict tied to concrete evidence, ensuring traceability for pre-merge reviews and CI gates.

Can I use pre-merge quality gates for multi-file code reviews?

Yes, pre-merge quality gates support scoped validation across multi-file changes. The verifier aggregates diffs and test results across all modified files to deliver a single evidence-based verdict for the entire code review workflow.

What inputs do I need to generate an evidence-based pass/fail verdict for a code change?

Generating an evidence-based verdict requires access to build outputs, test results, and change diffs. The verifier aggregates these inputs to evaluate whether the implementation meets acceptance criteria and returns a formal pass or fail decision.

Does the verifier work for incomplete work or exploratory design tasks?

No, the verifier does not apply to incomplete work, exploratory design, or tasks needing bug diagnosis. It only evaluates completed implementations that require a formal acceptance decision or scope compliance validation before merge.

What is the best way to automate scope compliance validation in a relay workflow?

Automating scope compliance validation in a relay or swarm workflow involves applying a formal quality gate to completed changes. The verifier checks implementation against acceptance criteria using build and test evidence to produce a clear verdict.