verify

Verify code or workflow changes by running tests, typecheck, and manual checks.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/cheafi/Trading-bot-CC --skill verify-cheafi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/cheafi/Trading-bot-CC/tree/main/.github/skills/verify
Command: npx skills add https://github.com/cheafi/Trading-bot-CC --skill verify-cheafi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents vague “it works” updates by forcing verification steps that produce concrete evidence before declaring a change complete.

Core Features & Use Cases

  • Evidence-first verification: Converts ambiguous completion claims into specific behaviors that must be proven.
  • Verification ladder: Uses existing tests first, then typecheck/build, then narrow direct command checks, and finally manual validation when automation is insufficient.
  • Transparent reporting: Outputs what was verified, which checks were run, what passed, and what failed or remains unverified.

Quick Start

Ask the AI to verify a specific behavior change by providing the exact claim to prove and any relevant commands, tests, or build steps available in your project.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify a code change actually works before declaring it complete?

To verify a code change, you must prove the specific behavior functions as claimed by running existing automated tests, typechecks, and direct commands, falling back to manual validation only when automation is insufficient.

What is evidence-first release readiness verification?

Evidence-first release readiness verification prevents vague completion claims by requiring concrete proof through CI checks and tests, transparently reporting passes, failures, and remaining unverified items before finalizing.

How to run build verification checks in order for a software change?

Run build verification checks in a specific order: execute existing tests first, then typecheck or build steps, then narrow direct command checks, and finally manual validation steps to produce reliable confidence.

Can I use manual validation when automated tests are insufficient for CI checks?

Yes, you can use manual validation when automated tests are insufficient for CI checks, provided you define the exact behavior to prove and transparently report the manual steps alongside any automated test passes or failures.

What is the best way to turn ambiguous completion claims into verified outcomes?

The best way to turn ambiguous completion claims into verified outcomes is to define the exact behavior to prove and run a verification ladder of checks, reporting only verified passes, failures, and unverified items.