Github Pr Formatting

Step 1: Build body in a temp markdown file

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

Step 2: Create draft PR using --body-file

gh pr create \
  --draft \
  --base develop \
  --head feature/my-branch \
  --title "feat(scope): concise title" \
  --body-file /tmp/pr-body.md

Safe Comment Posting Pattern

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

Single-line Bodies (Allowed)

If a body/comment is truly one line, --body "..." is acceptable.

If content is more than one line, use --body-file.

Formatting Checklist (Before Submit)

• Body written as Markdown file, not escaped string
• No literal \n in command body argument
• Title follows conventional commits style when appropriate
• Validation commands are listed
• PR is draft unless user asked for ready-for-review

Quick Anti-Patterns (Do Not Use)

• gh pr create --body "## Summary\n- item"
• gh pr comment --body "line1\nline2"
• Very long unstructured paragraph bodies

Quick Recovery If It Already Happened

If a PR body/comment was posted with literal \n:

1. Rebuild a proper markdown file.
2. Update PR body:

gh pr edit <pr-number-or-url> --body-file /tmp/pr-body.md

3. For comments, post a corrected replacement comment with --body-file.

Canonical Minimal Template

## Summary
- <what changed>
- <what changed>

## Validation
- <command>
- <command>