git-commit-messages

Format git commit messages using a single quoted -m multiline string.

2|Updated Nov 11, 2025

Search Tags:#git #workflow #formatting #bash #commit-messages #heredoc #multiline

Ready to run

npx skills add https://github.com/boneskull/claude-plugins --skill git-commit-messages

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit-messages
Source: https://github.com/boneskull/claude-plugins/tree/main/plugins/tools/skills/git-commit-messages
Command: npx skills add https://github.com/boneskull/claude-plugins --skill git-commit-messages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formats multi-line git commit messages without relying on HEREDOC syntax, preventing shell-related issues and ensuring consistency across environments.

Core Features & Use Cases

Single -m multiline messages: embed the entire commit message in quotes.
Clear guidance for body text, co-authors, and attribution notes in commits.
Suited for Bash scripts, CI pipelines, and manual commits that require a detailed message.

Quick Start

Provide a single -m string containing the full commit message.

Frequently Asked Questions about git-commit-messages

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

FAQPage Schema

How do I format git commit messages with multiple lines without using HEREDOC?▼

To format multi-line git commit messages without HEREDOC, use a single -m string with the entire message enclosed in quotes. This approach prevents shell-related issues in Bash workflows and ensures consistency across different environments.

Why does using HEREDOC cause issues with git commit messages in Bash?▼

Using HEREDOC for git commit messages causes shell-related issues because it can behave inconsistently across different environments. Formatting the commit message with a single -m multiline string avoids these HEREDOC syntax problems and ensures reliable execution.

Can I include co-author footers and body text in a single git commit -m string?▼

Yes, you can include co-author footers and body text in a single git commit -m string. By enclosing the entire multiline message in quotes, you can embed detailed body text and attribution notes cleanly within the standard Bash command.

What is the best way to automate multi-line git commit messages in CI pipelines?▼

The best way to automate multi-line git commit messages in CI pipelines is to use a single -m string. Formatting the entire message, including body text and footers, within quotes prevents HEREDOC issues and guarantees consistent commits across automated environments.

Does this formatting method require any external dependencies or components?▼

No, this formatting method requires no external dependencies or components. It works natively within Bash by enforcing a single -m string enclosed in quotes, making it suitable for manual commits and automation without additional tooling.

When should I not use a single -m string for git commit messages?▼

You should not use a single -m string if your workflow explicitly depends on HEREDOC syntax. This formatting method forbids HEREDOC usage entirely, requiring the entire multiline commit message to be enclosed in a single quoted string instead.