Skip to content

docs(#294): add cross-repo ordering guidance to PR body instructions #295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rh-hemartin merged 1 commit into from
Jul 22, 2026
Merged

docs(#294): add cross-repo ordering guidance to PR body instructions #295

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions skills/code-implementation/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -782,6 +782,14 @@ from step 6 and structure `pr_body` to match its sections. Otherwise,
write a best-effort description covering what changed, why, testing
approach, and any caveats.

**Cross-repo ordering:** When the motivating issue references a
different repository (e.g., a failure observed in an upstream repo),
lead the summary with what files in **this** repository are changing
and why. Place cross-repo references in a secondary "Context" or
"Related" subsection — not in the opening sentence. Reviewers read
the first line to orient themselves; leading with an external repo
reference can mislead them about which repository the PR targets.

Use a quoted heredoc to capture `pr_body` content without shell
expansion, then pass it to `jq --arg`:

Expand Down
Loading