do-commit

Automating code quality checks before a git commit involves running linters, tests, and type checkers to catch errors early. This process verifies that code adheres to project standards and ensures changes are production-ready before finalizing the commit.

Cleaning up temporary files before committing code removes artifacts and unnecessary files that should not be included in version control. This ensures the repository stays clean and prevents accidental commits of transient build outputs.

Checking for stale documentation and debug statements involves scanning changes for issues like commented-out code, secrets, and outdated CHANGELOG.md or README.md files. This self-review process ensures documentation is updated and the code is clean before review.

You can run a quick commit mode to perform automated checks and commit changes without executing the full test and build suite. This provides a faster workflow when you need to finalize minor changes while still maintaining basic quality gates.

Generating a commit message after passing quality gates delegates the message creation to a dedicated write-commits skill. This happens automatically once all temporary files are cleaned, documentation is verified, and self-review checks are complete.

Using a quality gate process for git commits prevents errors by running linters, type checkers, and self-review scans before finalizing changes. This ensures code adheres to project standards, catches debug statements, and verifies documentation is not stale.