conventional-commit

Name: conventional-commit
Availability: InStock
Author: vndkubi

Generate conventional commit messages from staged changes.

Updated Mar 4, 2026

Search Tags:#automation #git #commit #semver #breaking-changes #conventional-commits #scopes

Ready to run

npx skills add https://github.com/vndkubi/bootstrap-toolkits --skill conventional-commit-vndkubi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/vndkubi/bootstrap-toolkits/tree/main/.github/skills/conventional-commit
Command: npx skills add https://github.com/vndkubi/bootstrap-toolkits --skill conventional-commit-vndkubi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate conventional commit messages from staged changes, ensuring consistency with team conventions and semantic versioning.

Core Features & Use Cases

Conventional Commit Enforcement: Applies types, scopes, and breaking-change indicators per the Conventional Commits spec.
Multi-line Bodies: Supports detailed descriptions for complex changes and accompanies optional footers.
Release-Ready Output: Produces a ready-to-use commit message for git commit -m or extended messaging.

Quick Start

Stage your changes and run the conventional-commit skill to generate a compliant commit message.

Frequently Asked Questions about conventional-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate conventional commit messages from staged git changes?▼

To generate conventional commit messages from staged git changes, stage your files and run the skill to analyze the diff, determine the type and scope, and output a ready-to-use message for git commit.

What are conventional commits and how do they support semantic versioning?▼

Conventional commits are a specification for structuring commit messages with types, scopes, and breaking-change indicators. This format supports semantic versioning by providing a clear history of changes for release automation.

How do I indicate breaking changes in my automated commit messages?▼

To indicate breaking changes in automated commit messages, the skill analyzes your staged changes and applies breaking-change indicators per the conventional commits spec, ensuring your semantic versioning tracks major updates correctly.

Can I include multi-line bodies and footers in a generated conventional commit?▼

Yes, you can include multi-line bodies and optional footers in a generated conventional commit. The skill supports detailed descriptions for complex changes and formats the extended messaging for git commit -m.

Do I need any external dependencies to format my git commits conventionally?▼

No external dependencies are required to format your git commits conventionally. The skill operates independently to analyze staged changes and produce release-ready output for your git workflow.