Guide · Agent skill
How to use the Multiline Commit Messages agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The multiline-commit-messages skill is a short set of instructions that tells an AI agent how to write multi-line git commit messages when it runs commands through a shell tool. Without it, agents often write the message with heredoc syntax, and the commit can end up containing the raw text of the command instead of your message. This guide explains what the skill changes, how to install it, how to trigger it, and where it does not help, so you can check whether it fits your workflow.
Multiline Commit Messagesprisma/orm · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Get the multiline-commit-messages skill ZIP from the skill's page on this site.
- 2Unzip into a skills folder. Unzip the file into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP.
- 4Ask for a multi-line commit. Request a git commit with a summary and body, so the agent uses the skill's guidance.
- 5Check the stored message. Run git log -1 to confirm the commit message has the correct line breaks and text.
What the skill makes the agent do
When an agent commits code through a shell tool, it often builds the commit message with a heredoc inside $(cat ...). The source says this pattern is fragile: the shell may not parse it correctly in that context, and the result can be the literal text of the command, such as $(cat <<'EOF' ..., stored as the commit message.
This skill changes that behaviour. It tells the agent never to use $(cat <<'EOF' ...) or $(cat <<EOF ...) for commit messages, and to pass the message as a single-quoted string with real line breaks instead.
- The skill is guidance only. It runs no code and uses no network access.
- It applies to commits made with git through a shell tool.
Install the skill
You can install the skill in one of three ways. Download the skill ZIP from the skill's page on this site and unzip it into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want it limited to one repository.
If you use the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into the project's .claude/skills/ folder
- Claude apps: upload the ZIP under Settings → Capabilities → Skills
Trigger the skill with natural requests
The skill's description says it applies when you use single-quoted strings for multiline git commit messages in the Shell tool. You do not need a special command. Ask the agent to commit your changes and mention a multi-line message, for example in a request like the ones below.
If the agent is about to write a heredoc for a commit, the skill's rule is meant to steer it to the single-quoted form instead.
- "Commit these changes with a summary line and a longer body explaining why."
- "Make a git commit for the login fix and include a couple of paragraphs describing the reason."
- "Commit the staged files and write a multi-line message."
Example of the expected commit command
The skill recommends a single-quoted string with embedded newlines. A short summary line comes first, a blank line follows, then the body. The agent runs a command shaped like this:
git commit -m 'short summary line
Longer body paragraph explaining why the change exists.
Additional context if needed.'What the skill needs and what it does not do
The skill requires git and a shell tool available to the agent. It runs no scripts and uses no network. Its only effect is the guidance it gives the agent about how to write the commit command.
Check the limits before relying on it. It does not cover commit messages that contain single quotes. A literal apostrophe ends a single-quoted string, and handling that case needs separate work the skill does not provide. It also has no effect in projects that do not use git or where agents cannot run shell commands.
- Requires: git and a shell tool available to the agent
- Runs scripts: no
- Uses network: no
- Not covered: commit messages containing single quotes
Tips for getting reliable results
Review the commit after the agent makes it. Run git log -1 to see the stored message and confirm the line breaks and text are correct.
If your messages often contain apostrophes, plan to write those messages another way or edit them after the commit, since the skill does not address that case.
- Check the result with git log -1 after each commit.
- Use the project install if only one repository needs this behaviour.
- Keep the summary line short and leave a blank line before the body.
git log -1What people use it for
- Committing a bug fix with a short summary line and a body explaining the reason.
- Making several commits in one session without garbled heredoc text in the messages.
- Standardising multi-line commit messages in a team that uses an agent with a shell tool.
Frequently asked questions
Is the multiline commit messages skill free?
The source does not state pricing or licence terms beyond Apache-2.0 for the repository. Check the licence on the skill's page before using it commercially.
What do I need to use this skill?
You need git and a shell tool available to the agent. The skill runs no scripts and uses no network, so it only changes how the agent writes commit commands.
How do I install the multiline commit messages skill?
Download the ZIP from the skill's page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps, you can upload the ZIP under Settings → Capabilities → Skills.
Why does my agent's commit message contain the text of the command?
The source explains that heredoc syntax inside $(cat ...) is fragile in the Shell tool and can store the raw command text as the commit message. This skill tells the agent to use single-quoted strings with real line breaks instead.
Does this skill work with commit messages that contain single quotes?
No. A literal apostrophe ends a single-quoted string, and the skill does not cover that case. You will need separate handling for those messages.
Does this skill work with other agents besides Claude Code?
The skill is aimed at agents that use a Shell tool to run git commands, such as Claude Code or similar agents. The source does not list other specific agents, so test it with yours before relying on it.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if an AI agent makes your git commits through a shell tool and you have seen garbled multi-line messages. It is a small, low-risk piece of guidance with no scripts and no network access. Skip it if your project does not use git or agents cannot run shell commands, or if your messages often contain single quotes, since the skill does not handle that case.
Download the skill