commit-hygiene

To enforce Conventional Commits across a git repository, you can automate validation of type, scope, subject, and length using git hooks. This skill configures husky and lint-staged to ensure messages meet conventional rules during local development and CI pipelines.

The best way to validate and fix non-compliant git commit messages is using an automated linter. This skill parses messages against the Conventional Commits specification and provides a --fix mode to automatically correct formatting issues before they reach your history.

To set up commitlint and husky hooks for local development, run the --setup command. This installs the necessary git hooks to enforce Conventional Commits, preventing team members from bypassing message validation checks during the commit process.

Yes, you can audit past git history for Conventional Commits compliance. By running the --check-history command, this skill reviews previous repository commits to identify any messages that violate the conventional type, scope, and length rules.

Yes, this commit linting approach works in CI pipelines. It provides phase-by-phase guidance to parse and enforce messages, making it suitable for CI pipelines and local development to ensure consistent histories and automated hooks.