Write git commit messages to a file and commit with git -F.
npx skills add https://github.com/bneb/perqed --skill git-commit-bneb
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/bneb/perqed/tree/main/.agents/skills/git-commit Command: npx skills add https://github.com/bneb/perqed --skill git-commit-bneb
This Skill helps developers avoid shell escaping issues when making git commits in zsh by guiding safe messaging practices and a reliable workflow.
Write the commit message to a file and commit using the file.
High-intent search queries and answers about installing and using this skill.
To commit multi-line git messages in zsh without escaping issues, write the message text to a temporary file and use the git -F option to read the commit message directly from that file.
Git commit -m breaks with special characters because shells like zsh apply escaping rules to the string, which mangles multi-line content or symbols before git receives the message.
The best way to format conventional commits safely in zsh is writing the formatted message to a file and committing from the file, ensuring the commit history remains readable and reproducible.
Committing from a file in git requires no extra dependencies, utilizing the native git -F option or equivalent to read the message directly from a written file instead of using shell flags.
Using heredoc for git commit messages in zsh often causes escaping issues, making a write-to-file approach combined with the git -F option a more reliable workflow for multi-line content.
ather-techieGenerate standardized git commit messages from staged changes and repository history.
SumitRajpalGenerate a Markdown changelog from Git history using conventional commits.
sulhicmzGenerate conventional commit messages from git diffs and staged changes.
JitsusamaFormat Git CLI commands with heredoc syntax and shell quoting rules for scripts.
