skills.rest
accolver
accolverCOMMUNITY
Explore all skills by this author →
Website𝕏@acolveGitHub

git-conventional-commits

Generate Conventional Commits messages from staged git changes.

4|Updated Mar 6, 2026
Search Tags:#automation#git#changelog#commit#code-quality#semver#conventional-commits
One-click install
npx skills add https://github.com/accolver/skill-maker --skill git-conventional-commits-accolver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-conventional-commits
Source: https://github.com/accolver/skill-maker/tree/main/git-conventional-commits
Command: npx skills add https://github.com/accolver/skill-maker --skill git-conventional-commits-accolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate conventional commit messages from staged git changes when the task is to name or format a commit, not to review code or write release notes.

Core Features & Use Cases

  • Conventional commits formatting: messages follow the form type(scope): description with an optional body and footer.
  • Ensure messages are parseable and compatible with semantic versioning tools, changelogs, and CI pipelines.
  • Use Case: when changes are staged for a feature or fix, produce a clear, scoped commit message that communicates intent.

Quick Start

Ask your agent to generate a conventional commit for the currently staged changes following the Conventional Commits specification.

Frequently Asked Questions about git-conventional-commits

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

FAQPage Schema
How do I generate conventional commit messages for staged git changes?▼

To generate conventional commit messages, the Skill analyzes your staged git changes and produces a formatted message with type, scope, subject, optional body, and footer. It ensures the output is parseable by semantic versioning and changelog automation tools.

What is the conventional commits format for structuring a git commit?▼

The conventional commits format structures git messages as type(scope): description, followed by an optional body and footer. This pattern categorizes changes like feat, fix, or refactor to support automated release workflows and changelog generation.

How do I automate semantic versioning and changelog generation from git commits?▼

Automating semantic versioning and changelog generation requires commits to follow the Conventional Commits specification. This Skill formats staged changes into parseable messages with proper types like feat or fix, enabling CI pipelines to determine version bumps automatically.

Can I use conventional commits for refactoring and documentation changes?▼

Yes, conventional commits apply to refactoring and documentation changes. The Skill categorizes staged git changes into appropriate types such as refactor, docs, feat, and fix, ensuring all modification categories adhere to the standard commit message pattern.

What are the limitations of using automated conventional commit messages?▼

This Skill is limited to generating commit messages from currently staged git changes and does not perform code review or write release notes. It focuses solely on formatting the commit message structure to support automation and release workflows.

Related Skills

Explore More Software Engineering Skills→
inakaminakam

conventional-commit

Generates Japanese Conventional Commit messages and executes git commits for detected repository changes.

Community
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
haJ1thaJ1t

release-manager

Automate release management by parsing conventional commits and generating changelogs.

Community
Advanced
ExsyDevExsyDev

aif-commit

Analyze staged git changes to generate Conventional Commits messages.

Community
Advanced