git-commit

To keep code and documentation synchronized before a git commit, validate implementation against design specs and update CHANGELOG.md, README.md, and DESIGN.md to reflect the changes before staging and pushing.

Update CHANGELOG and history log by reviewing git diffs after a bug fix, aligning the changes with design specs, updating ~/history.log if present, and preparing a clean git commit and push.

Automated documentation validation works for refactoring changes by verifying the implementation matches design specs and ensuring README.md and DESIGN.md are updated before the final git push.

The best way to enforce a docs update workflow in git is to apply an end-to-end process that reviews git diffs, aligns with design specs, updates history logs, and performs the final git commit and push.

You do not need a history.log file present to automate your git commit workflow; the process updates ~/history.log only if it already exists before preparing the commit and pushing.