correct-git-commits-no-exceptions

Conventional commit messages are enforced by auditing the current changeset to remove debug code and transient language, then generating terse, insightful messages tailored to staff-grade standards. This hygiene pass runs automatically before commit creation to ensure compliance.

Commit hygiene prevents messy, time-bound, or under-explained commits from entering long-lived repositories. It removes transient language and cruft while rewriting vague wording into timeless descriptions, ensuring the project history remains clean and maintainable for senior audiences.

Documentation accuracy is verified by checking affected READMEs and docs against the implementation. The process ensures examples still work, APIs match the code, and options remain accurate, without unnecessarily expanding the documentation scope.

Yes, automated commit hygiene applies to both human-authored and agent-generated commits or pull requests. It performs a current-changeset hygiene pass, executes required tests, and generates standards-compliant messages regardless of the commit author.

Tests are ensured to pass by requiring test execution as a mandatory step before commit creation. The process runs the required test suite, verifies documentation correctness, and removes debug code, blocking commits until all standards are met.

Automated git commit hygiene passes should not be used when you need to preserve transient language or debug code intentionally. The process removes obvious low-signal comments and debug cruft, rewriting vague wording into timeless descriptions, which may alter original intent.