Execute affected-package tests and bind results to the resolving commit.
npx skills add https://github.com/anthony-chaudhary/fak --skill verify-anthony-chaudhary
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
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.
Run the verify skill to check the current commit by executing the affected-package tests and grading the binding against the repository witness.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
barretstorckVerify task completion with executed commands and output before asserting success.
cdcoonceManage GitLab repositories, issues, merge requests, and CI/CD pipelines via glab terminal commands.
jordanhubbardAutomate pre-commit code review with static analysis and security scans.
Sheldon-92Execute test suites and report failures with coverage metrics.
