conventional-commit

Generate Conventional Commits messages with type, scope, subject, body, and footer.

Updated Mar 1, 2026

Search Tags:#git #developer tools #version control #commit #conventional commits #code history

Ready to run

npx skills add https://github.com/SirPedr/saga --skill conventional-commit-sirpedr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/SirPedr/saga/tree/main/.agents/skills/conventional-commit
Command: npx skills add https://github.com/SirPedr/saga --skill conventional-commit-sirpedr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers create standardized and informative Git commit messages, improving code history clarity and automation.

Core Features & Use Cases

Enforces Conventional Commits: Guides users to follow the widely adopted Conventional Commits specification.
Improves Readability: Ensures commit messages are consistent, understandable, and machine-readable.
Use Case: When committing a new feature, use this Skill to ensure your commit message follows the feat(<scope>): <subject> format, including a clear explanation of the change and its motivation.

Quick Start

Use the conventional-commit skill to generate a commit message for a new feature that adds user authentication.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema

How do I write conventional commit messages for Git?▼

To write conventional commit messages for Git, structure your commit with a type, optional scope, and subject, such as `feat(auth): add user authentication`. This format improves code history clarity and enables automated changelog generation.

What are the different commit types in the Conventional Commits specification?▼

The Conventional Commits specification supports various commit types including feat, fix, chore, docs, style, refactor, perf, test, build, and ci. Each type categorizes the nature of your Git code changes for semantic versioning.

How do automated changelogs and semantic versioning work with structured Git commits?▼

Automated changelogs and semantic versioning rely on structured Git commits to parse code history. By using types like `feat` for new features or `fix` for bug fixes, tools can automatically determine version bumps and generate release notes.

Does this conventional commit generator support adding a body and footer to my Git commit?▼

Yes, the conventional commit generator supports structuring Git commit messages with a type, scope, subject, body, and footer. This allows you to include detailed explanations of the change and its motivation beyond the standard subject line.

What is the best way to format a Git commit message for a new feature?▼

The best way to format a Git commit message for a new feature is using the `feat(<scope>): <subject>` structure. Following the Conventional Commits specification ensures your message is consistent, machine-readable, and suitable for semantic versioning.