commit

This Skill automates generating conventional commits in Git by guiding you to select commit types, scopes, and descriptions, ensuring a standardized and readable Git commit history following the <type>(<scope>): <description> format.

The conventional commits format structures code history using the <type>(<scope>): <description> pattern. Predefined types like feat, fix, and docs categorize changes, while scopes identify the affected project area for clear code evolution tracking.

Co-author information is added to a Git commit message through optional body fields provided during the automated commit generation process. This appends attribution details directly into the commit metadata alongside your conventional commit description.

Yes, project-specific branch naming rules are supported when creating Git commits. The Skill checks branch names against your project configurations to ensure code history aligns with your repository's naming conventions before finalizing the commit message.

The best way to determine commit scopes for changed files is using automated scope suggestions based on your modified codebase. The Skill analyzes changed files and helps identify the appropriate scope to append to your commit type.

You need to use conventional commits for version control when you want a clean, standardized, and informative code history. It makes code evolution understandable for collaborators by clearly stating what was changed, why, and in which project area.