hook-violation-recovery

To handle git pre-commit hook violations safely, use hook violation recovery to analyze the failed contract and choose a deliberate path: either override with documented ratification or revise the acceptance criteria to resolve the failure traceably.

The best way to document a hook override is to enforce an audit trail that logs the violation rationale and decision documentation, ensuring the override is deliberate and traceable rather than a silent bypass of the CI pipeline.

You need to revise a contract instead of overriding a pre-push hook when the violation indicates an outdated or incorrect acceptance criteria, requiring you to update the contract to address the violation rather than ratifying the failure.

Yes, you can use this process for CI pipeline failures because it is applicable in development workflows with pre-commit, pre-push hooks, and CI pipelines to manage contract violations and ensure accountability.

Ratification overrides a hook violation with a documented decision, while AC revision updates the contract itself to address the violation, providing two distinct decision paths for managing local hook failure modes.

You should avoid silent bypasses when git hooks fail to ensure traceable, deliberate responses that maintain security and accountability best practices, preventing untracked contract violations from entering the development workflow.