format-commit-message

Generate conventional commit messages with Claude Code attribution.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ronmikailov/site-360 --skill format-commit-message-ronmikailov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: format-commit-message
Source: https://github.com/ronmikailov/site-360/tree/main/.claude/skills/format-commit-message
Command: npx skills add https://github.com/ronmikailov/site-360 --skill format-commit-message-ronmikailov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate standardized conventional commit messages with Claude Code attribution, ensuring consistent history across releases, fixes, and docs.

Core Features & Use Cases

  • Generate conventional commit messages following project standards with optional scope and an optional body.
  • Include attribution in the commit message to credit Claude Code.
  • Use for release commits, automated version updates, refactors, and documentation changes.

Quick Start

Tell the AI the commit type, optional scope, and a brief description to produce a formatted commit message.

Frequently Asked Questions about format-commit-message

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

FAQPage Schema
How do I automate conventional commit messages with Claude Code attribution?

Automate conventional commit messages with Claude Code attribution by providing the commit type, optional scope, and a brief description to generate a standardized message. This enforces consistent formatting and proper crediting across your development workflow.

What is the conventional commit format for automated release and documentation commits?

The conventional commit format standardizes release and documentation commits by enforcing a specific type, scope, and description length. Using this format ensures consistent project history across automated version updates, refactors, and docs.

Can I include an optional body and scope when generating standardized commit messages?

Yes, you can include an optional scope and an optional body when generating standardized commit messages. You simply provide the commit type, desired scope, and description to produce a properly formatted conventional commit message.

Does this workflow enforce description length and commit type for conventional commits?

Yes, this workflow enforces description length and commit type for conventional commits to maintain project standards. It strictly applies the conventional commit format, scope, and description length while automatically including Claude Code attribution.

Why add attribution to automated git commit messages?

Adding attribution to automated git commit messages credits Claude Code for its role in development workflows. This maintains transparency in your git history while ensuring standardized conventional commit formatting for releases, fixes, and documentation updates.