Open clean draft PRs and post correctly formatted comments/bodies without escaped newline artifacts.
Use this skill whenever creating PRs, editing PR descriptions, or posting multi-line PR comments.
Ensure PR titles, bodies, and comments render as proper Markdown and never appear with literal escaped sequences like \n.
--body-file / --body-file -)."line1\nline2").## Summary## Validation## Scope / Notes (optional)cat > /tmp/pr-body.md <<'EOF'
## Summary
- change 1
- change 2
- change 3
## Validation
- npm run lint
- npm test -- <focused-tests>
## Scope / Notes
- out-of-scope note (if needed)
EOF
--body-filegh pr create \
--draft \
--base develop \
--head feature/my-branch \
--title "feat(scope): concise title" \
--body-file /tmp/pr-body.md
For multi-line PR comments:
cat > /tmp/pr-comment.md <<'EOF'
## Update
- addressed X
- deferred Y (reason)
EOF
gh pr comment <pr-number-or-url> --body-file /tmp/pr-comment.md
If a body/comment is truly one line, --body "..." is acceptable.
If content is more than one line, use --body-file.
\n in command body argumentgh pr create --body "## Summary\n- item"gh pr comment --body "line1\nline2"If a PR body/comment was posted with literal \n:
gh pr edit <pr-number-or-url> --body-file /tmp/pr-body.md
--body-file.## Summary
- <what changed>
- <what changed>
## Validation
- <command>
- <command>