What problem does it solve? Before handing off a completed implementation checkpoint, teams need objective evidence that the change set actually works. This Skill defines a verification contract that runs the minimum sufficient formatter, static, test, build, and diff-integrity checks, then returns an evidence-backed verdict instead of an unverified claim of completion. ## Core Features & Use Cases - Scoped verification contract: Establishes the complete change and comparison point from accepted task context and Git state, then selects only owner-supported verification surfaces. - Ordered evidence pipeline: Runs normalization first, then non-mutating static checks, directly owned tests, and broader surfaces justified by risk, with each surface reported as passed, failed, inconclusive, or not applicable. - Deterministic verdicts: Returns exactly one of semantic_fix_required, failed, inconclusive, or passed based on trustworthy evidence, while preserving HEAD, the index, and user-owned files. - Use Case: After an agent finishes implementing a feature in a repository, invoke this Skill to verify the checkpoint with the project's own formatter, linters, and tests, and receive a passed verdict or precise diagnostics routed back to the implementation owner. ## Quick Start Ask the agent to verify the current completed change set in this repository using its change-set-verification Skill and report the verdict with evidence.
