Git Commit Convention

To enforce a strict git commit message format, this Skill validates every commit against the <type>(<scope>): <subject> convention, ensuring consistent types, scopes, and subjects across all project commits.

Pre-commit checks should include running tests, linting, and type checks to validate code quality. This Skill provides a pre-commit checklist that ensures both code validation and commit message quality are completed before committing changes.

A commit convention policy works by intercepting the git workflow to validate commit message structure before finalizing the commit. This Skill applies strict formatting rules to all commits across the project, guiding types, scopes, subjects, and optional body or footer text.

No external dependencies are required to apply this git commit convention. The Skill operates independently to enforce the Bedriftsgrafen project's strict commit message format and pre-commit policies without relying on additional components.

You should use the <type>(<scope>): <subject> commit format for every commit in a project that requires strict consistency. This Skill enforces this specific format, along with optional body and footer sections, to maintain a standardized git history across the entire project.

The best way to automate git commit linting is to integrate a pre-commit policy that checks message format and runs code validation. This Skill enforces commit conventions and guides pre-commit checks including tests, linting, and type checks to ensure quality before committing.