recording-changes

To enforce a consistent git commit workflow, you must stage changes and emit compliant messages so pre-commit hooks pass. This ensures changes are recorded atomically and project conventions are maintained without ad-hoc commits.

The best way to stage batch product changes and ADR drafts is to use a controlled workflow that validates your branch, stages the batch atomically, and commits with a compliant message to preserve a deterministic git history.

Yes, you need a defined base branch in your repository to use pre-commit guardrails for recording changes. The workflow expects this setup to validate branches and properly guard the commit process.

To recover from pre-commit hook failures when committing design artifacts, you follow the error recovery workflow designed to gracefully handle hook failures while maintaining clear history and pre-commit integrity.

You should use atomic commits instead of ad-hoc commits because they ensure changes are recorded consistently, maintain clear history, enforce pre-commit integrity, and follow project conventions for a deterministic branch strategy.