pre-push-validation

Pre-push validation automatically checks if your critical documentation files—CLAUDE.md, README.md, and CHANGELOG.md—have been updated since your oldest unpushed commit. If they haven't, it blocks the push until documentation is current.

Pre-push validation monitors three files: CLAUDE.md for AI instructions and project context, README.md for project overview, and CHANGELOG.md for tracking changes. It verifies each has been updated relative to your unpushed commits.

Yes, pre-push validation runs automatically as a git hook before every push. It detects uncommitted changes and validates file recency without requiring manual checks.

Pre-push validation compares the modification timestamps of CLAUDE.md, README.md, and CHANGELOG.md against your oldest unpushed commit. If documentation hasn't been updated since that commit, the hook flags it as outdated and prevents the push.

Pre-push validation blocks the push and alerts you that documentation is outdated relative to your code changes. You must update the relevant files and commit them before the push succeeds.

Yes, pre-push validation checks all unpushed commits in your current branch. It identifies the oldest unpushed commit and ensures documentation has been refreshed since that point to reflect all pending changes.