Repository navigation
ref(skill): Defer to the shared Sentry skills in create-java-pr - #6621
Merged
Merged
Conversation
getsentry/skills renamed create-pr to pr-writer and then removed the old name, so Step 5 called a skill that no longer exists. Keep the repo PR template as the body structure over pr-writer's default shape, as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
📲 Install BuildsAndroid
|
Branch naming, commit format, and PR title format now come from create-branch, commit, and pr-writer instead of local copies that had already drifted (the commit types lacked revert). Add #skip-changelog to the first PR body instead of editing it afterwards, and write PR bodies to per-branch or per-PR files. The shared /tmp/pr-body.md outlives sessions and once opened a PR with another PR's body. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
runningcode
marked this pull request as ready for review
November 16, 2026 13:43
runningcode
requested review from
0xadam-brown and
romtsn
and removed request for
a team
November 16, 2026 13:43
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit c37c75b. Configure here.
runningcode
commented
Nov 17, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
adinauer
approved these changes
Nov 17, 2026
adinauer
left a comment
Member
There was a problem hiding this comment.
looks like this could use the wrong tmp file
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

📜 Description
So this does 2 things
create-java-prskill now refers to thepr-writerinstead of thecreate-prskill. getsentry/skills renamedcreate-prtopr-writer(ref(skills): Promote pr-writer and skill-writer as canonical names skills#79) in March. So you'll need to update your getsentry/skills.Here's a summary from my agent of the duplicates and simplification.
sentry-skills:create-branch, Step 3 relies onsentry-skills:commitfor the message format, and Step 5 invokessentry-skills:pr-writerfor the title. The local copies of these rules are gone. They had already drifted: the allowed commit types were missingrevert.pr-writer's default short body.#skip-changelognow goes into the first PR body. Before, the PR was created first and its body was downloaded, edited and re-uploaded just to add that line./tmp/pr-body.md.💡 Motivation and Context
getsentry/skills renamed
create-prtopr-writer(getsentry/skills#79) and then removed the old name (getsentry/skills#110), so Step 5 called a skill that no longer exists./tmp/pr-body.mdsurvives between sessions and is also the filepr-writeruses. If writing the new body failed,ghuploaded whatever an earlier session left there. That is how #6187 was opened with another PR's body, which GitHub then linked to issue #6175.💚 How did you test it?
This PR was opened by following the updated Step 5, and this description was updated with the updated "Editing PR Descriptions" procedure.
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
None.
🤖 Generated with Claude Code
#skip-changelog