compose:verify

Enforces running verification commands before claiming work is complete or passing.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/HKUST-QUANT-SOCIETY/quantcode --skill compose-verify-hkust-quant-society
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compose:verify
Source: https://github.com/HKUST-QUANT-SOCIETY/quantcode/tree/main/.opencode/meta-skills/verify
Command: npx skills add https://github.com/HKUST-QUANT-SOCIETY/quantcode --skill compose-verify-hkust-quant-society

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers often claim work is complete, tests pass, or bugs are fixed without actually running the verification commands, leading to broken builds, shipped defects, and lost trust. This Skill enforces an evidence-first discipline so no success claim is made without fresh command output. ## Core Features & Use Cases - Verification Gate: Defines a mandatory five-step gate (identify command, run it, read output, verify result, then claim) before any completion statement. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed, agent completed) to the exact evidence required and what does not count as proof. - Rationalization Blocking: Lists red-flag phrases and excuses ("should work", "just this once", "linter passed") that signal an unverified claim is about to be made. - Use Case: Before committing a bug fix, the agent runs the test suite, confirms zero failures in the output, and only then reports the fix as verified, including for regression tests via a red-green cycle check. ## Quick Start Before claiming any task is done or tests pass, run the relevant verification command, read the full output, and only then state the result with the evidence.

Frequently Asked Questions about compose:verify

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

FAQPage Schema
How do I verify tests pass before committing code?

Run the full test command fresh in the current session, read the complete output, and confirm zero failures and a clean exit code. Only then state that tests pass, citing the actual result rather than relying on a previous run.

What counts as evidence that a bug is fixed?

A bug is verified fixed only by re-running a test that reproduces the original symptom and observing it pass. Changing the code or assuming the fix works does not count as evidence.

Does a passing linter mean the build succeeds?

No. A linter checks style and static issues but does not compile or bundle the code. Build success requires running the actual build command and confirming it exits with code 0.

How do I verify a regression test actually works?

Use a red-green cycle: write the test, confirm it passes with the fix, revert the fix and confirm the test fails, then restore the fix and confirm it passes again. A test that never fails proves nothing.

Can I trust an agent's report that a task succeeded?

No. Agent success reports must be independently verified by inspecting the version control diff and confirming the actual changes match the claimed work before reporting completion.