ref(docs): Avoid shell redirects in PR workflow docs

[adinauer]

📜 Description

Replaces shell redirect examples (>, >>, |, &&) with Write/Edit tool instructions in pr.mdc and the create-java-pr skill.

Three places updated:

• pr.mdc § "Stack List in PR Description" — the update-PR-body example
• create-java-pr Step 5.5 — stack list update instructions
• create-java-pr Step 6 — skip-changelog instructions

💡 Motivation and Context

When agents follow the current examples literally, they run compound shell commands like gh pr view 5172 --json body --jq '.body' > /tmp/pr-body.md. The > redirect makes it a compound shell expression that no longer matches the simple Bash(gh pr view *) permission pattern, causing a permission prompt for every PR in the stack.

By instructing agents to use Write/Edit tools for file I/O and keep gh commands simple, the existing permission patterns work without extra approvals.

💚 How did you test it?

Manual review of the instructions. The issue was observed during a stacked PR workflow where every gh pr view triggered a permission prompt.

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

None — self-contained change.

#skip-changelog

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

This PR will not appear in the changelog.

---

_{🤖 This preview updates automatically when you update the PR.}

[sentry]

Sentry Build Distribution

App	Version	Configuration
SDK Size	8.34.1 (1)	release

[lbloder]

LGTM 👍

One possible improvement: We could tell the agent to delete the temp file after updating.

[adinauer]

One possible improvement: We could tell the agent to delete the temp file after updating.

Yeah we could do that in the future