Can I automate changelogs with this skill?

Yes, by following these commit patterns, you can use tools like standard-version to automatically generate and update your CHANGELOG.md file based on your commit history.

What are Conventional Commits?

Conventional Commits is a lightweight convention for commit messages that provides a set of rules for creating an explicit commit history, making it easier to write automated tools on top of.

How does this skill support Semantic Versioning?

It maps specific commit types to SemVer levels: 'feat' for MINOR, 'fix' for PATCH, and the '!' or 'BREAKING CHANGE' footer for MAJOR updates.

How do I enforce these commit rules in my project?

This skill provides configuration examples for Husky and Commitlint, which act as Git hooks to reject any commit messages that do not follow the standardized format.

Conventional Git Commits

Name: Conventional Git Commits
Author: Naw3

byNaw3

Developer Tools

Enforces standardized Git commit messages and workflows to enable automated semantic versioning and changelog generation.

About

The Conventional Git Commits skill provides a comprehensive framework for implementing the Conventional Commits specification within any development project. It guides users through writing structured, machine-readable commit messages, setting up automated linting with tools like Husky and Commitlint, and managing semantic versioning triggers. By standardizing commit types, scopes, and breaking change indicators, this skill helps teams maintain a clean repository history, simplify code reviews, and fully automate the release process and changelog documentation.

Key Features

Automated changelog generation patterns
Standardized branch naming and Pull Request title conventions
Semantic versioning (SemVer) mapping for automated releases
Git hook integration using Husky and Commitlint configuration
Standardized commit message formatting (type, scope, subject)
0 GitHub stars

Use Cases

Enforcing consistent commit standards across a multi-developer team
Improving project traceability and the readability of Git history
Automating the generation of release notes and version bumps

About

Key Features

Automated changelog generation patterns
Standardized branch naming and Pull Request title conventions
Semantic versioning (SemVer) mapping for automated releases
Git hook integration using Husky and Commitlint configuration
Standardized commit message formatting (type, scope, subject)
0 GitHub stars

Use Cases

Enforcing consistent commit standards across a multi-developer team
Improving project traceability and the readability of Git history
Automating the generation of release notes and version bumps