verification-before-completion

Enforce verification before claiming code completion by requiring tests, linting, and builds to run with documented outcomes. This skill implements explicit verification steps, records results as evidence, and ensures transparent reporting prior to PRs or releases.

Evidence-based verification for PRs and releases involves running tests, linting, and builds, then collecting the outputs into an audit-ready report. It ensures all checks pass and attaches a verifiable report showing test results and build status before declaring success.

Attach test results and build status to a PR by triggering the verification flow to run tests, lint, and build commands. Review the outputs and attach the collected verification evidence before making any completion claim.

Yes, evidence-based completion works within Cursor agent interactions by implementing explicit verification steps and ensuring transparent reporting. It records test, linting, and build results as evidence directly within the agent workflow.

Require verification before claiming work success in code reviews because claiming work as complete without verification leads to quality issues and erodes trust among teams. Documenting outcomes ensures transparent, audit-ready reporting.