write-conventional-commit

Generates Git commit messages conforming to the Specifications 1.0.0 format.

5|Updated Feb 21, 2026

Search Tags:#code quality #git #developer tools #versioning #commit #conventional commits

Ready to run

npx skills add https://github.com/ragnarok22/agent-skills --skill write-conventional-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-conventional-commit
Source: https://github.com/ragnarok22/agent-skills/tree/main/skills/write-conventional-commit
Command: npx skills add https://github.com/ragnarok22/agent-skills --skill write-conventional-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of Git commit messages that adhere to the Conventional Commits specification, ensuring consistency and clarity in your project's history.

Core Features & Use Cases

Automated Message Generation: Drafts commit messages based on code changes and user intent.
Conventional Commit Compliance: Enforces the type(scope)!: description format, including optional bodies and footers.
Use Case: When you've finished a bug fix, use this Skill to generate a fix: <description> commit message, automatically including a BREAKING CHANGE: footer if the fix is not backward-compatible.

Quick Start

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

Frequently Asked Questions about write-conventional-commit

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

FAQPage Schema

How do I generate a conventional commit message from staged Git changes?▼

To generate a conventional commit message from Git changes, this Skill analyzes your staged diff and drafts a compliant message. It automatically selects the appropriate commit type, defines an optional scope, and composes the header, body, and footer.

What is the Conventional Commits 1.0.0 specification format for Git commits?▼

The Conventional Commits specification enforces a structured format for Git commits using `type(scope)!: description`. This Skill automates applying this format, ensuring your project history maintains consistent structure, clarity, and standardized versioning.

How do I add a breaking change footer to a Git commit automatically?▼

To add a breaking change footer to a Git commit, this Skill detects non-backward-compatible changes during message generation. It automatically appends a `BREAKING CHANGE:` trailer to the commit message footer when required by your diff.

Can I convert a free-form Git commit message into a conventional commit?▼

You can convert a free-form Git commit message into a conventional commit using this Skill. It processes your existing text and reconstructs it into the compliant `type(scope)!: description` format with optional bodies and footers.

Do I need any external dependencies to create compliant conventional commits?▼

You do not need any external dependencies to create compliant conventional commits with this Skill. It operates independently with internal scripts and references to generate and apply Git commit messages directly.

What is the best way to apply a commit type and scope when versioning code?▼

The best way to apply a commit type and scope during code versioning is using this Skill to draft your message. It handles type selection and optional scope definition based on your code changes to ensure Conventional Commits compliance.