Skip to content

chore: Add Cursor Bugbot PR review guidelines (JAVA-721) - #6046

Open
runningcode wants to merge 3 commits into
mainfrom
no/bugbot-review-guidelines
Open

chore: Add Cursor Bugbot PR review guidelines (JAVA-721)#6046
runningcode wants to merge 3 commits into
mainfrom
no/bugbot-review-guidelines

Conversation

@runningcode

@runningcode runningcode commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

📜 Description

Adds .cursor/BUGBOT.md, a rules file for Cursor Bugbot PR review.

Read the file, not much explaining here to do. We should probably update the AGENTS.md file to be consistent with this too.

💡 Motivation and Context

💚 How did you test it?

Not applicable — no code changes. Behavior will be visible on the next PRs Bugbot reviews, and the rules can be tuned from there.

📝 Checklist

  • I added GH Issue ID & Linear ID
  • I added tests to verify the changes. — n/a, no code changes
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed. — this is the doc
  • I updated the wizard if needed. — n/a
  • Review from the native team if needed. — n/a
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.
  • Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec. — no public API changes

🔮 Next steps

#skip-changelog

Bugbot reviews PRs against generic Java advice unless the repo tells it
what this SDK actually cares about. This adds .cursor/BUGBOT.md, the same
location sentry-javascript, sentry-dart, and sentry-react-native use.

The rules are drawn from this repo's own invariants: the narrow-catch rule
and ExceptionUtils.rethrowIfFatal, binary compatibility and the
IScope/IScopes implementation fan-out, opt-in-by-default options, cost
added to the Android main-thread init path, span origin and op
conventions, and monotonic-vs-wall clock selection. Formatting, PR title
format, and changelog entries are listed as out of scope, since Spotless,
validate-pr, and Danger already enforce them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@sentry

sentry Bot commented Sep 2, 2026

Copy link
Copy Markdown

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings

Re-wrap the bullets that ran long and add the missing blank line after
the Concurrency and Clocks headings, so the file matches the wrapping
used throughout. No wording changes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@runningcode runningcode changed the title chore: Add Cursor Bugbot PR review guidelines chore: Add Cursor Bugbot PR review guidelines (JAVA-721) Sep 2, 2026
@linear-code

linear-code Bot commented Sep 2, 2026

Copy link
Copy Markdown

JAVA-721

@runningcode
runningcode marked this pull request as ready for review September 2, 2026 14:25
@runningcode runningcode added the sanity-check PR needs a lightweight review for obvious issues label Sep 2, 2026
Comment thread .cursor/BUGBOT.md
Comment thread .cursor/BUGBOT.md Outdated
Comment thread .cursor/BUGBOT.md Outdated
Comment thread .cursor/BUGBOT.md
Comment thread .cursor/BUGBOT.md Outdated
Comment thread .cursor/BUGBOT.md Outdated
Comment thread .cursor/BUGBOT.md Outdated
Comment thread .cursor/BUGBOT.md
Comment thread .cursor/BUGBOT.md
Add checks for reflection keep rules, SAGP bytecode manipulation,
threading models on new classes, clock arithmetic misuse, dependency
bump intent, and contract-focused tests.

Require broad catches to justify themselves in a code comment rather
than the PR description, so the reasoning stays with the code. Narrow
the test requirement to customer-facing behavior, and drop the `.api`
and IScope/IScopes rules now covered elsewhere.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Comment thread .cursor/BUGBOT.md Outdated
Comment thread .cursor/BUGBOT.md
Comment thread .cursor/BUGBOT.md
Comment thread .cursor/BUGBOT.md

@markushi markushi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Look great, already curious about the upcoming bot feedback we'll get.

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

Labels

sanity-check PR needs a lightweight review for obvious issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add bugbot to repo

2 participants