Git Hook

Outcome: Use Git Hook to release or recover the change safely, with a clear record. User context: A pre-commit hook quickly checks staged files for format problems and secrets, then shows clear fixes. Hooks on a developer's computer are not copied by default, so they cannot be the only security gate. Delivery concept or operation: Git Hook. Why it fits: Use this term for fast local automation or server rules at a documented Git step. Do not use it when: Do not keep slow, unclear, destructive, or machine-specific required checks only in local hooks. Delivery requirements: Name the code repository and target. List preconditions, changes, review and CI checks, conflict and data-loss risks, release order, and the rollback or recovery command. Repository safeguards: Keep unpublished work and a clear history. Do not run destructive steps without an explicit backup. Check the exact code diff and remote target before publishing. Acceptance criteria: Review the intended diff and pass all required checks. Keep the target version traceable. Practice failure recovery and keep published history clear. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Repository, branch, team activity, release environment, approval owner, protected checks, and rollback target.