verify

Enforce verification command execution and evidence review before completion claims.

15|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/duronext/jig --skill verify-duronext
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/duronext/jig/tree/main/core/skills/verify
Command: npx skills add https://github.com/duronext/jig --skill verify-duronext

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.

Core Features & Use Cases

  • Enforces a gate before declaring completion.
  • Requires running a verification command, reviewing full output, and citing evidence.
  • Suitable for CI/build workflows, pull requests, and release readiness checks.

Quick Start

Run the verification command and review the output before making any success claim.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I prevent premature completion claims before creating a pull request?

Preventing premature completion claims requires running a verification command, reading the full output, and validating the evidence before making any success assertions.

What is a verification gate in CI and build workflows?

A verification gate in CI and build workflows is an enforced checkpoint that requires running verification commands and collecting fresh evidence before allowing a commit, PR, or deployment to proceed.

How do I enforce evidence collection before a deployment?

To enforce evidence collection before a deployment, run a verification command, read the full output to confirm success, and validate the evidence before declaring the work complete.

Do I need specific dependencies to run verification checks before committing?

No specific dependencies are required to run verification checks before committing. You only need a verification command to execute and the ability to review the full output and validate the evidence.

What is the best way to verify build success before claiming a fix is passing?

The best way to verify build success before claiming a fix is passing is to enforce a gate that requires executing a verification command and confirming the full output before making any success claim.

When should I not rely on a verification gate for release readiness?

You should not rely on a verification gate for release readiness if you cannot execute a verification command or if you are unable to review the full output and validate the evidence before making a claim.