Skip to content

docs(agents): Make create-java-pr defer to pr.mdc for conventions - #5931

Closed
runningcode wants to merge 1 commit into
mainfrom
no/create-java-pr-defer-to-rules
Closed

docs(agents): Make create-java-pr defer to pr.mdc for conventions#5931
runningcode wants to merge 1 commit into
mainfrom
no/create-java-pr-defer-to-rules

Conversation

@runningcode

Copy link
Copy Markdown
Contributor

📜 Description

Trims the overlap between the create-java-pr skill and .cursor/rules/pr.mdc.

The skill already declared pr.mdc "the source of truth," then restated most of it anyway — branch naming, commit message conventions, the full PR body template, the changelog subsection table, the entry format, and the stack list warnings all lived in both files.

  • create-java-pr/SKILL.md — keeps the parts that are genuinely its own: the ordered procedure and the Step 0 branch-type detection heuristic, which pr.mdc doesn't cover. Every convention now links to the owning pr.mdc section instead of restating it.
  • pr.mdc — the inlined PR body template is replaced by a pointer to .github/pull_request_template.md, so the template exists in one place rather than three.
  • pr.mdc — commit subject limit corrected from 100 to 70 characters, matching Sentry's commit message conventions.

Net −123/+49 lines.

💡 Motivation and Context

Duplicated conventions drift. The PR template in particular existed in three copies (.github/pull_request_template.md, pr.mdc, and the skill), so a change to the real template would silently leave two stale copies that agents keep using.

💚 How did you test it?

Docs only, no code changes. Verified that all six pr.mdc sections the skill now references resolve to real headings in that file.

📝 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

Independent of #5930, which removes coding.mdc/overview_dev.mdc. No file overlap between the two.

#skip-changelog

The skill declared pr.mdc the source of truth and then restated most of it
anyway: branch naming, commit conventions, the full PR template, the
changelog subsection table, entry format, and the stack list warnings all
existed in both files. Two copies of the same conventions drift apart.

Keep the procedure in the skill (ordered steps and the branch-type
detection heuristic, which pr.mdc does not cover) and point at pr.mdc for
each convention. Also drop the inlined PR template from pr.mdc in favor of
.github/pull_request_template.md, so the template lives in one place, and
correct the commit subject limit from 100 to 70 characters to match
Sentry's commit message conventions.
@sentry

sentry Bot commented Aug 11, 2026

Copy link
Copy Markdown

📲 Install Builds

Android

🔗 App Name App ID Version Configuration
SDK Size io.sentry.tests.size 8.52.0 (1) release

⚙️ sentry-android Build Distribution Settings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant