skills.rest
javiertelioz
javierteliozCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

conventional-commit

Generate standardized commit messages conforming to the Conventional Commits specification.

Updated Mar 16, 2026
Search Tags:#git#workflow#validation#xml#commit-message#conventional-commits
One-click install
npx skills add https://github.com/javiertelioz/my-personal-marketplace --skill conventional-commit-javiertelioz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/javiertelioz/my-personal-marketplace/tree/main/plugins/conventional-commit/skills/conventional-commit
Command: npx skills add https://github.com/javiertelioz/my-personal-marketplace --skill conventional-commit-javiertelioz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of standardized, descriptive commit messages aligned with the Conventional Commits specification, reducing ambiguity and improving historical traceability.

Core Features & Use Cases

  • Enforces a consistent commit message format across a project.
  • Validates type, scope, and description against the Conventional Commits rules.
  • Provides examples and guidance for common scenarios (features, fixes, docs, chores).

Quick Start

Generate a conventional commit for a feature addition with the message type 'feat', scope 'auth', and description 'add login retry on authentication failure'.

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 feature updates?▼

To generate conventional commit messages, use a structured format with fields for type, scope, and description. For feature updates, apply the 'feat' type with a specific scope like 'auth' and a concise description of the change.

What is the conventional commits specification for git workflow validation?▼

The conventional commits specification standardizes commit messages using an XML-based structure with type, scope, description, body, and footer fields. This validation ensures historical traceability and reduces ambiguity across software development workflows.

How do I validate commit message types and scopes against conventional commits rules?▼

Validating commit message types and scopes involves checking them against conventional commits rules. The process verifies that the type (like feat or fix), scope, and description conform to the specification, providing examples and guidance for common scenarios.

Can I use conventional commit formatting for multi-module workstreams?▼

Yes, conventional commit formatting applies to multi-module workstreams. The XML-based structure supports defining specific scopes for different modules, ensuring consistent commit message standards across single-repo projects and complex multi-module development environments.

Does conventional commit validation work for chore and documentation updates?▼

Conventional commit validation works for chore and documentation updates by supporting message types like 'docs' and 'chore'. It provides examples and guidance for these scenarios, ensuring all routine updates maintain the same standardized commit format as features and fixes.

Related Skills

Explore More Software Engineering Skills→
kos3nzkos3nz

git-commit

Generate conventional commit messages by analyzing Git diffs.

Community
Advanced
Unique-AGUnique-AG
5

changelog-pyproject

Update CHANGELOG.md and pyproject.toml versions from commit history.

Official
Intermediate
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced
AsiaOstrichAsiaOstrich
70

commit-standards

Generate and validate commit messages following the Conventional Commits specification.

Community
Intermediate