skills.rest
RussianLioN
RussianLioNCOMMUNITY
Explore all skills by this author →
GitHub

format-commit-message

Generate conventional commit messages with type, scope, description, body, and breaking changes.

1|Updated Feb 13, 2026
Search Tags:#code quality#automation#git#developer tools#conventional commits#commit message
One-click install
npx skills add https://github.com/RussianLioN/moltinger --skill format-commit-message-russianlion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: format-commit-message
Source: https://github.com/RussianLioN/moltinger/tree/main/.claude/skills/format-commit-message
Command: npx skills add https://github.com/RussianLioN/moltinger --skill format-commit-message-russianlion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of standardized, conventional commit messages, ensuring consistency and clarity in your project's version control history.

Core Features & Use Cases

  • Conventional Commits: Generates messages adhering to the conventional commit specification (type, scope, description, body, footer).
  • Automated Attribution: Automatically includes Claude Code attribution for generated messages.
  • Use Case: When creating a new feature, use this Skill to generate a feat commit message, ensuring it's properly scoped and described according to project standards.

Quick Start

Use the format-commit-message skill to create a feat commit with the description "add user authentication".

Frequently Asked Questions about format-commit-message

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

FAQPage Schema
How do I generate conventional commit messages automatically?▼

To generate conventional commit messages automatically, this Skill formats your commit type, scope, description, body, and breaking changes into a standardized structure with Claude Code attribution for consistent git history.

What is a conventional commit and when do I need it for git?▼

A conventional commit standardizes version control history by structuring messages with type, scope, description, body, and footer. You need it to maintain clarity and consistency in automated commits, release commits, and feature additions.

How do I structure a feat commit with scope and breaking changes?▼

To structure a feat commit, provide the type, scope, description, body, and breaking changes as input. The Skill formats these elements according to conventional commit project standards and appends automated attribution.

Does this commit formatter require specific input fields to work?▼

Yes, the commit formatter requires input for type, scope, description, body, and breaking changes to accurately format the git commit message according to conventional commit project standards.

What's the best way to standardize automated git commits in development?▼

The best way to standardize automated git commits is using a formatter that applies conventional commit specifications and includes automated Claude Code attribution for consistent version control history.

Related Skills

Explore More Software Engineering Skills→
maxmurrmaxmurr

generating-commit-messages

Generate commit messages from git diff --staged with WHAT/WHY summaries.

Community
Basic
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
sunLeeesunLeee

check-commit-message

Validate Git commit messages against Conventional Commits rules.

Community
Intermediate
craigtkhillcraigtkhill

write-commit-message

Generate git commit messages following conventional commits syntax.

Community
Basic