multiline-commit-messages · git:20260517.7c3f443 · 2026-05-17 · sha256 064f41e656ca6091
multiline-commit-messages git:20260517.7c3f443A
Immutable. This exact content never changes and is served at /api/v1/blob/064f41e656ca6091.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_k7rldhvdoia7tyaw/064f41e656ca609186d81ff43b693fa9737bca2c64437b3f5765a5b94a355a70.json
Then /plugin install multiline-commit-messages@markdownregistry-k7rldhvdoia7tyaw in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: multiline-commit-messages description: >- Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages. --- # 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: ```bash 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: ```bash 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.