using-commit

Write commit messages following the Conventional Commits specification.

Updated Feb 10, 2026

Search Tags:#git #changelog #developer tools #versioning #commit #conventional commits

Ready to run

npx skills add https://github.com/jrodrigopuca/skills --skill using-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: using-commit
Source: https://github.com/jrodrigopuca/skills/tree/main/using-commit
Command: npx skills add https://github.com/jrodrigopuca/skills --skill using-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you write clear, consistent, and machine-readable commit messages that improve project history and enable automation.

Core Features & Use Cases

Standardized Commit Messages: Follows the Conventional Commits specification for structured messages.
Automated Changelogs & Versioning: Enables tools to automatically generate changelogs and manage semantic versioning.
Use Case: Before committing your code changes, use this Skill to ensure your commit message follows the feat(scope): description format, including a breaking change notice if necessary.

Quick Start

Use the using-commit skill to write a commit message for adding a new user authentication feature.

Frequently Asked Questions about using-commit

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

FAQPage Schema

How do I write conventional commit messages for automated changelog generation?▼

To write conventional commit messages for automated changelog generation, structure your commits using the feat, fix, or other type prefixes with an optional scope, like feat(scope): description, to ensure a clear, machine-readable history. This enables tools to automatically generate changelogs and manage semantic versioning.

What is the conventional commits specification format for breaking changes?▼

The conventional commits specification format for breaking changes requires adding a ! after the type or scope, or including a BREAKING CHANGE footer. This structured format ensures automated tools can detect breaking changes and properly increment the major semantic version number.

How do I structure git commit messages for features and fixes?▼

To structure git commit messages for features and fixes, use the feat type for new functionality and fix for bug corrections, followed by an optional scope in parentheses and a clear description. This standardization facilitates automated semantic versioning and changelog generation.

Can I use conventional commits to automate semantic versioning?▼

Yes, you can use conventional commits to automate semantic versioning. By adhering to the specification with structured types like feat and fix, tools can parse your machine-readable history to automatically determine and apply the correct version bumps.

What are the best practices for machine-readable git commit history?▼

Best practices for machine-readable git commit history involve strictly following the conventional commits specification, using defined types, scopes, and breaking change notices. This structured approach improves project history clarity and enables automated changelog generation and semantic versioning.