verification

Automated verification before a pull request requires executing pytest, mypy, ruff lint, ruff format check, and pre-commit hooks, then validating their outputs and exit codes as evidence of readiness.

A verification gate is a process that runs a predefined suite of checks including unit tests, type checks, linting, formatting, and pre-commit validation before any completion claim to ensure software quality.

You enforce evidence-before-claim practices by running pytest on unit tests and mypy type checks, requiring their full outputs and exit codes to be documented and validated before asserting success.

Yes, the verification process supports running ruff format checks and pre-commit hooks alongside pytest and mypy, validating all five command outputs and exit codes before declaring work complete.

The best way to validate work before declaring a feature branch complete is to run the full verification cycle of pytest, mypy, ruff lint, ruff format, and pre-commit hooks, ensuring all checks pass with documented outputs.

Claiming work complete without verification poses risks because it allows misrepresentations and unverified code to enter the codebase, bypassing unit tests, type checks, and linting that gate PR readiness.