The Context section of skills/ce-commit/SKILL.md says not to join commands with ;, &&, ||, pipes, $(...) or redirects, because that syntax fails under Windows PowerShell. Step 6's canonical example then does exactly that:
git add file1 file2 file3 && git commit -m "$(cat <<'EOF'
...
EOF
)" -- file1 file2 file3
On PowerShell this is a parse error (Missing file specification after redirection operator — reproduced on pwsh 7 / Windows 11), so an agent on a PowerShell-shelled harness reaches the commit step and either fails or has to pick which of the two instructions to ignore. AGENTS.md even points at ce-commit as the reference for the argv-only pattern.
Two separate calls plus multiple -m flags produce the same subject-plus-body message on any shell (each extra -m becomes a blank-line-separated paragraph), and keep the load-bearing trailing pathspec. Tested on pwsh and bash. PR incoming.
The Context section of
skills/ce-commit/SKILL.mdsays not to join commands with;,&&,||, pipes,$(...)or redirects, because that syntax fails under Windows PowerShell. Step 6's canonical example then does exactly that:On PowerShell this is a parse error (
Missing file specification after redirection operator— reproduced on pwsh 7 / Windows 11), so an agent on a PowerShell-shelled harness reaches the commit step and either fails or has to pick which of the two instructions to ignore. AGENTS.md even points atce-commitas the reference for the argv-only pattern.Two separate calls plus multiple
-mflags produce the same subject-plus-body message on any shell (each extra-mbecomes a blank-line-separated paragraph), and keep the load-bearing trailing pathspec. Tested on pwsh and bash. PR incoming.