verify-this

Verify claims with baseline and treatment evidence comparison.

3|Updated Apr 8, 2025
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill verify-this-zanzythebar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-this
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/verify-this
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill verify-this-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns vague claims like "did this fix it" or "prove it works" into falsifiable statements backed by repeatable local evidence, replacing subjective recaps with measured before-and-after comparisons. ## Core Features & Use Cases - Baseline/Treatment Comparison: Captures evidence from the old state (merge base, parent commit, failing branch) and the changed state using identical commands, data, and environment. - Multiple Verification Surfaces: Supports code tests, CLI transcripts, UI screenshots, API response diffs, performance timings, and memory heap snapshots. - Strict Verdicts: Returns exactly one of VERIFIED, NOT VERIFIED, or INCONCLUSIVE with raw metrics and reasoning. - Use Case: After fixing a performance regression, ask the assistant to verify the fix; it measures the parent commit and the patched code with the same benchmark and reports whether the claimed threshold was met. ## Quick Start Ask the assistant to verify that your recent fix actually resolved the bug by comparing behavior before and after the change.

Frequently Asked Questions about verify-this

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

FAQPage Schema
How do I verify that a bug fix actually works?

Restate the fix as a falsifiable claim with a metric and threshold, then capture a baseline from the parent commit or failing branch and a treatment from the changed code using the same command and environment. Compare the raw outputs and report VERIFIED only if the difference matches the prediction.

How to compare performance before and after a code change?

Run the same benchmark on the old state (merge base or parent commit) and the new state with identical data, warmup, and machine. Compare timings or CPU profiles directly; the claim is verified only if the delta meets the claimed threshold without confounds.

What evidence counts when verifying a UI or CLI behavior claim?

Acceptable evidence includes terminal transcripts, demo recordings, screenshots, accessibility snapshots, browser traces, and HTTP request/response diffs. The same surface and procedure must be used for both baseline and treatment captures.

When is a verification result inconclusive?

A result is INCONCLUSIVE when there is no valid baseline, the signal is too noisy, the measurement failed, or an environment difference invalidates the comparison. It does not mean the claim is false, only that the evidence cannot decide it.

Can verification artifacts contain sensitive data?

Yes, artifacts like screenshots, HTTP bodies, prompts, and heap snapshots may contain sensitive content. In that case only minimal inline evidence is kept unless the user explicitly agrees to writing artifacts to disk under /tmp/verify-this.