Automates tiered verification producing VERIFIED/UNVERIFIED verdicts and an evidence state file.
npx skills add https://github.com/paulingham/.claude --skill verify-paulingham
Please help me install this Agent Skill. Skill: verify Source: https://github.com/paulingham/.claude/tree/main/skills/verify Command: npx skills add https://github.com/paulingham/.claude --skill verify-paulingham
Verifying software features goes beyond passing tests; this Skill provides a structured workflow that proves correctness through contract, smoke, mutation, and end-to-end tests.
Provide a feature change and trigger the verify workflow to produce a tiered verification report and the verification_evidence.json state file.
High-intent search queries and answers about installing and using this skill.
Multi-tier verification proves feature correctness by orchestrating contract, smoke, mutation, and end-to-end tests in a single workflow, exposing verification gaps that standard testing misses. It generates structured verdicts and evidence state for backend, frontend, and integration changes.
You automate these checks by providing a feature change and triggering the multi-tier verification workflow. The process orchestrates contract, smoke, mutation, and e2e tests across your changes, outputting a tiered verification report and a verification_evidence state file.
Yes, multi-tier verification applies to backend, frontend, and integration changes. It orchestrates contract, smoke, mutation, and end-to-end checks across these scopes and supports optional oracle comparisons to validate correctness when available.
The best way to track verification evidence is using an automated workflow that writes a verification_evidence state file. It produces clear VERIFIED, UNVERIFIED, or VERIFIED_WITH_SKIP signals to report structured verdicts for your CI pipeline.
Mutation testing fits into automated verification as one of multiple orchestrated tiers alongside contract, smoke, and e2e checks. It exposes verification gaps by validating test effectiveness, contributing to the final VERIFIED or UNVERIFIED verdict.
An UNVERIFIED status occurs when the multi-tier verification workflow exposes correctness gaps across contract, smoke, mutation, or e2e checks. Passing tests alone does not prove feature correctness, which is why structured verdicts capture gaps.
ananddtyagiValidate API contracts against backend implementations and generate TypeScript clients.
genesis-agentsCross-check claims against cited sources and return verdicts with evidence.
AnveioRun and debug repository verification pipelines with ./verify.sh and E2E modes.
haposoftAutomates execution and verification of unit, integration, e2e, and UI tests.
