verify

Execute shell commands and evaluate outputs to verify claims with PASS/FAIL evidence.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill verify-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/verify
Command: npx skills add https://github.com/arbazkhan971/godmode --skill verify-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes uncertainty by converting subjective claims about code, tests, builds, performance, or endpoints into reproducible command executions and unambiguous PASS/FAIL evidence so decisions are based on proof rather than trust.

Core Features & Use Cases

  • Evidence-first verification: derive or accept a shell command, execute it, capture stdout/stderr/exit code and duration, and evaluate against a strict pass condition.
  • Staleness and flakiness detection: detect changed sources that void prior results, run numeric checks multiple times and require median consistency, and treat partial results as failures.
  • Audit trail and logging: write detailed TSV logs and local evidence files for every verification run, with clear failure reasons and recovery suggestions.
  • Use Case: confirm "tests pass", verify "coverage > 80%", or prove an HTTP endpoint returns 200 with concrete command output and a PASS/FAIL verdict.

Quick Start

Run /godmode:verify on the claim "Tests pass" to execute the test command, read full output, and produce a PASS or FAIL evidence report.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify CI checks and test suites with command execution evidence?

Verify endpoint responses by executing shell commands that capture HTTP outputs and exit codes, then evaluate against strict pass conditions like 200 status codes. This produces unambiguous PASS or FAIL evidence with concrete command output for endpoint verification.

What is the best way to detect flaky tests and check numeric thresholds in CI?

Detect flaky tests by running numeric checks multiple times and requiring median consistency across repeated runs. Changed sources that void prior results are flagged, and partial results are treated as failures to ensure reliable threshold verification for software projects.

How do I log verification runs and maintain an audit trail for test evidence?

Log verification runs by writing detailed TSV logs and local evidence files for every execution. Each audit entry is timestamped and includes failure reasons and recovery suggestions, ensuring a complete audit trail for all command execution and claim verification activities.

Does this command execution verification work for local builds and performance thresholds?

Command execution verification works for local builds, performance thresholds, test suites, and endpoint responses. It applies to CI checks by capturing command outputs and evaluating them against strict pass or fail conditions to generate definitive evidence for software projects.