conventional-commits

To write conventional commits, follow the type(scope): description format by selecting a commit type like feat or fix, defining a scope if applicable, and summarizing your staged changes to ensure code history readability and CI/CD automation compatibility.

The conventional commits format is a standardized structure for git commit messages using type(scope): description. You need it to make commit history machine-readable, enabling automated version control and clear communication of features, bug fixes, or maintenance tasks.

Yes, you can use custom scopes in conventional commit messages. The Skill provides specific guidance for defining scopes, such as using 'skills' for skill-related changes or CI/CD workflows, while also explaining when to omit scopes entirely for broader updates.

You should use commit types like feat, fix, docs, style, refactor, test, perf, ci, chore, and build for conventional commits. Each type clearly indicates whether the staged change introduces a new feature, a bug fix, or a maintenance task.

Conventional commits are important for CI/CD pipelines because they ensure commit messages are strictly machine-readable. This standardization allows automated systems to reliably detect changes, triggering appropriate build, test, or deployment workflows based on the commit type.