verify

Execute verification commands and validate outputs for completion claims.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/SentioLabs/agent-nexus --skill verify-sentiolabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/SentioLabs/agent-nexus/tree/main/claude-marketplace/plugins/arc/skills/verify
Command: npx skills add https://github.com/SentioLabs/agent-nexus --skill verify-sentiolabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate completion claims by running defined verification commands and collecting fresh evidence, preventing premature or unverifiable closures.

Core Features & Use Cases

  • Ensures verification gates are executed before declaring work done, including running tests, builds, and status checks.
  • Automates validation of outputs (exit codes, test results, and status) to guarantee claims are supported by fresh evidence.
  • Useful in CI/CD workflows, issue tracking gates (ARC), and release readiness checks across projects.

Quick Start

Run the full verification workflow and present the proof outputs.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify completion claims with fresh evidence before closing an issue?

Verify completion claims by executing defined verification commands and validating outputs to ensure work is supported by fresh evidence. It prevents premature closures by running builds, tests, and status checks before declaring work done.

What is evidence-based verification in CI workflows and release readiness checks?

Evidence-based verification validates completion claims by executing verification commands and collecting fresh evidence. It enforces verification gates in CI workflows and release readiness checks by automating output validation to guarantee claims are supported.

How do I run verification gates for CI tests and builds using arc issue tracking?

Run verification gates across run, read, and verify steps for software projects using arc issue tracking. The workflow executes CI tests and builds, checks exit codes, enforces zero failures, and produces a reproducible verification report.

Can I automate validation of test results and exit codes to prevent unverifiable closures?

Yes, you can automate validation of outputs including exit codes, test results, and status to guarantee claims are supported by fresh evidence. This automation prevents premature or unverifiable closures by enforcing verification gates.

Does the verification workflow work without external dependencies or components?

Yes, the verification workflow operates without external dependencies or components. It validates completion claims by running defined verification commands and collecting fresh evidence directly within your software engineering environment.

Why should I enforce fresh verification evidence instead of relying on previous test runs?

Enforce fresh verification evidence to prevent premature or unverifiable closures. Relying on previous test runs risks invalid completion claims, whereas executing defined verification commands guarantees current exit codes and zero failures are validated.