multiline-commit-messages

multiline-commit-messages is a skill for Claude Code, Codex from prisma/prisma-next. It costs 35 tokens per session (281 once invoked), scanned A, a copy of multiline-commit-messages, Apache-2.0.

A guideline for writing multi-line messages in Git commits, which record changes in a Git repository. It specifies a shell-safe way to include a summary and longer explanation.

In plain words
What is it for?
Use it when creating a Git commit with a multi-line message from the shell.
Why use it?
It avoids malformed commit messages caused by fragile shell heredoc syntax. The intended message remains readable and is stored correctly.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit Use it when creating a Git commit with a multi-line message from the shell.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/prisma/prisma-next/multiline-commit-messages
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add prisma/prisma-next --skill multiline-commit-messages
Clone the repo
git clone --depth 1 https://github.com/prisma/prisma-next

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for multiline-commit-messages

README.md
[![agentmods](https://agentmods.dev/badge/skills/prisma/prisma-next/multiline-commit-messages/github.svg)](https://agentmods.dev/skills/prisma/prisma-next/multiline-commit-messages)
Your own site
<a href="https://agentmods.dev/skills/prisma/prisma-next/multiline-commit-messages"><img src="https://agentmods.dev/badge/skills/prisma/prisma-next/multiline-commit-messages/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for multiline-commit-messages

Your own site · 80×15
<a href="https://agentmods.dev/skills/prisma/prisma-next/multiline-commit-messages"><img src="https://agentmods.dev/badge/skills/prisma/prisma-next/multiline-commit-messages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 281 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00281
Opus 5.5 $0.00014 $0.00112
Sonnet 5.5 $0.00007 $0.00056
Haiku 4.5 $0.00003 $0.00028

Measured 1mo ago against content hash 064f41e656ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

multiline-commit-messages scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to multiline-commit-messages — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills-contrib/multiline-commit-messages/SKILL.md · 39 lines

What it actually says

Multiline commit messages

The Shell tool sends commands as a single string. Heredoc syntax (<<'EOF') inside $(cat ...) is fragile and fails silently — the literal $(cat <<'EOF' ... ends up as the commit message instead of the intended text.

Rule

Never use $(cat <<'EOF' ...) or $(cat <<EOF ...) for commit messages.

Use single-quoted strings with embedded newlines:

git commit -m 'short summary line

Longer body paragraph explaining why the change exists.
Additional context if needed.'

Why heredocs fail

The Shell tool passes the command as a single string argument. When you write:

git commit -m "$(cat <<'EOF'
message
EOF
)"

The shell may not parse the heredoc correctly in this context — the EOF delimiter, newlines, and nested quoting interact unpredictably. The result is the raw $(cat <<'EOF' ... text appearing as the commit message.

Single-quoted strings with literal newlines are simple, portable, and always work.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 39 lines · 35 tokens per session scan A 064f41e656ca

Subscribe to this mod's changes

multiline-commit-messages is a skill published in the GitHub repository prisma/prisma-next (414 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 281 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to multiline-commit-messages, differing in 0 lines, and is treated as a copy.