skills.rest
lluppesms
lluppesmsCOMMUNITY
Explore all skills by this author →
GitHub

conventional-commit

Generate conventional commit messages using a structured XML format.

Updated Nov 21, 2025
Search Tags:#git#developer tools#commit#conventional commits#code history
One-click install
npx skills add https://github.com/lluppesms/dadabase.demo --skill conventional-commit-lluppesms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/lluppesms/dadabase.demo/tree/main/.github/skills/conventional-commit
Command: npx skills add https://github.com/lluppesms/dadabase.demo --skill conventional-commit-lluppesms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers create standardized, descriptive commit messages that adhere to the Conventional Commits specification, improving code history clarity and automation.

Core Features & Use Cases

  • Guided Commit Message Generation: Provides a structured XML format and examples for crafting commit messages.
  • Workflow Integration: Guides users through staging changes and automatically commits with the generated message.
  • Use Case: A developer needs to commit a new feature. They use this Skill to ensure their commit message is correctly formatted as feat(scope): description, including an optional body and footer for breaking changes.

Quick Start

Use the conventional-commit skill to generate a commit message for your staged changes.

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 for git?▼

To generate conventional commit messages, this Skill uses a structured XML format with predefined types like feat and fix to standardize your git commit history. It guides you through staging changes and automatically commits with the generated message.

What is the conventional commits specification and why use it?▼

The conventional commits specification standardizes commit messages using structured types and scopes to improve code history clarity. It enforces a consistent format like feat(scope): description to facilitate automated changelog generation.

How do I format a git commit message for breaking changes?▼

To format a git commit message for breaking changes, the Skill enforces a structured XML format that includes an optional body and footer. This ensures your conventional commit message correctly flags breaking changes in your code history.

Can I integrate conventional commits into my software development workflow?▼

Yes, you can integrate conventional commits into your software development workflow. The Skill provides workflow integration by guiding you through staging changes and automatically committing them with the standardized generated message.

Do I need any dependencies to create standardized commit messages?▼

No dependencies are required to create standardized commit messages. The Skill operates independently using predefined types and a structured XML format to enforce the conventional commits specification for your git history.

Related Skills

Explore More Software Engineering Skills→
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
hyukudanhyukudan
1

git-workflow

Guide Git version control workflows with branching strategies and commit standards.

Community
Intermediate
Cor-IncorporatedCor-Incorporated
4

git-commit-helper

Generate conventional commit messages by analyzing git diffs.

Official
Intermediate