
Multiline Commit Messages
- 2 installs
- 418 repo stars
- Updated August 3, 2026
- prisma/prisma-next
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.
About
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages. name: multiline-commit-messages description: >-
- Use single-quoted strings for multiline git commit messages in the Shell tool.
- **Never** use `$(cat <<'EOF' ...)` or `$(cat <<EOF ...)` for commit messages.
- Configuration patterns for multiline-commit-messages.
- Evidence-backed steps from upstream documentation.
- When-to-use criteria for multiline-commit-messages versus alternatives.
Multiline Commit Messages by the numbers
- 2 all-time installs (skills.sh)
- Ranked #1,839 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
multiline-commit-messages capabilities & compatibility
- Capabilities
- multiline commit messages quick start · multiline commit messages when to use guidance · multiline commit messages integration patterns
What multiline-commit-messages says it does
Use single-quoted strings for multiline git commit messages in the Shell tool.
Prevents heredoc escaping failures that produce garbled commit messages.
npx skills add https://github.com/prisma/prisma-next --skill multiline-commit-messagesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 418 |
| Last updated | August 3, 2026 |
| Repository | prisma/prisma-next ↗ |
How do I use multiline-commit-messages correctly?
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.
Who is it for?
Teams implementing multiline-commit-messages workflows from the catalog.
Skip if: Skip when requirements clearly match a different specialized stack.
When should I use this skill?
User asks about multiline-commit-messages, use single-quoted strings for multiline git commit messages in the shell tool. prevents he.
What you get
Working multiline-commit-messages setup with validated configuration and next steps.
Files
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.
Related skills
FAQ
What does multiline-commit-messages do?
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.
When should I use multiline-commit-messages?
User asks about multiline-commit-messages, use single-quoted strings for multiline git commit messages in the shell tool. prevents he.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.