validate-fix

Pre-commit plan validation prevents code drift by computing a diff against HEAD, reading your plan file, and reporting deviations to ensure implementations match the agreed scope before a commit is finalized.

Yes, pre-commit validation can enforce required error handling and type checks, detect missing tests, and generate a structured validation report that acts as a commit blocker if quality assurance criteria are not met.

Dual-LLM validation cross-references your uncommitted changes against the original plan, identifying unplanned modifications and type errors to enforce quality assurance and block commits that deviate from the agreed implementation.

The best way to check for unplanned modifications is to run a pre-commit validation process that reads your plan file, computes a diff of current changes, and flags any deviations from the agreed implementation scope.

Yes, you need an existing plan file to perform plan validation, as the process relies on reading the agreed plan to compute a diff against HEAD and accurately report any implementation deviations or missing tests.

Automated commit blockers for high-risk implementations rely on a pre-existing plan file to detect deviations, meaning they cannot validate changes effectively if the implementation lacks a clearly defined plan or structured test requirements.