verify

Execute affected-package tests and bind results to the resolving commit.

30|12|Updated Jun 21, 2026

Search Tags:#code quality #automation #git #testing #verification #go

Ready to run

npx skills add https://github.com/anthony-chaudhary/fak --skill verify-anthony-chaudhary

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill verify-anthony-chaudhary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common pitfall of assuming a code change is complete simply because the diff looks correct, ensuring that done-claims are backed by actual test execution.

Core Features & Use Cases

Test-Bound Validation: Ensures that a resolving commit is only marked as done if its affected-package tests have explicitly run and passed.
State Transparency: Clearly distinguishes between successful test runs (CLAIM_TEST_GREEN), failed runs (CLAIM_TEST_RED), and unrun states (CLAIM_TEST_UNRUN).
Use Case: Use this after committing a feature to verify that the affected packages pass their tests, preventing the accidental merging of code that passes a shape check but fails its own logic tests.

Quick Start

Run the verify skill to check the current commit by executing the affected-package tests and grading the binding against the repository witness.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I verify code changes are complete before merging in Go?▼

Test-bound validation distinguishes between successful test runs (CLAIM_TEST_GREEN), failed runs (CLAIM_TEST_RED), and unrun states (CLAIM_TEST_UNRUN). This state transparency prevents assuming a code change is complete simply because the diff looks correct.

How do I run affected-package tests against a resolving git commit?▼

Use the verification skill after committing a feature to execute affected-package tests and grade the binding against the repository witness. This ensures the resolving commit is only marked done if tests explicitly run and pass.

Do I need a witness sidecar to automate test-bound verification?▼

Yes, integrating with the repository's test seam and witness sidecar is required. This setup ensures accurate reporting of test-bound done-claims by validating the completion status of code changes.

What is the best way to prevent accepting untested code changes in automation workflows?▼

Bind done-claims to verified test results to prevent accepting untested code changes. This approach validates completion status by executing affected-package tests and binding results to the resolving commit, ensuring only tested changes are accepted.

Why does code that passes a shape check still fail verification?▼

Verification executes affected-package tests to validate actual logic, not just diff appearance. This catches code that passes a shape check but fails its own logic tests, ensuring done-claims are backed by real test execution.

When should I not use automated test-bound validation for git commits?▼

Avoid automated test-bound validation if your repository lacks a test seam and witness sidecar. Without these integrations, the system cannot execute affected-package tests or accurately report test-bound done-claims for resolving commits.