Git Commits

This is a strict guideline. Follow these rules exactly.

How to format and create git commits, branches, and PRs when helping developers.

🚨 Pre-Commit Gates

Before generating commit messages, run the pre-commit-check skill against all staged files. This covers:

1. Security — credentials, secrets, .env files (delegates to security-checklist)
2. Code quality — DRY, naming, error handling, dead code (references core-principles)
3. Breakage risks — build, tests, Lambda invocations, missing env vars

Do not proceed to commit grouping until all three gates pass.

After running the gates, briefly confirm the result and which path was used:

• "Pre-commit check passed (via pre-commit-check skill) — no security issues, code quality OK, build verified."