git-conventions

Conventional commits enforce a standardized message format using type prefixes like feat, fix, docs, and refactor. Enable pre-commit hooks or CI checks to validate commits match the syntax and follow rules like imperative mood, subject line under 72 characters, and no trailing periods.

Conventional commits standardize git history with structured messages (type: scope: description) to improve traceability, automate release notes, and enable teams to quickly understand what changed and why. It applies across feature branches, PRs, and release workflows.

Yes. This skill filters sensitive files and provides guidance for integrating pre-commit checks and CI validation to catch and block secret leaks before commits reach the repository.

Configure a pre-commit hook or add CI checks to enforce conventional commit syntax, validate subject length under 72 characters, require imperative mood, and filter sensitive data. Apply consistently across all developers and branches.

Yes. Conventional commits apply across feature branches, pull requests, and release workflows, enabling consistent history tracking and automated generation of release notes based on commit types and scopes.

The standard includes feat, fix, docs, refactor, test, chore, style, and perf types with optional scopes. Each type signals the nature of the change, supporting automated release note generation and history classification.