chore: add guardrails for PR's#1902
Merged
Merged
Conversation
|
d459e34 to
90831b4
Compare
erangeles
approved these changes
May 29, 2026
apucacao
approved these changes
May 29, 2026
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.
Summary
Updating ./cursor/BUGBOT.md
Screenshots (if appropriate):
Testing approaches
Note
Low Risk
Documentation-only change to
.cursor/BUGBOT.md; no runtime, API, or dependency impact.Overview
Extends
.cursor/BUGBOT.mdwith a PR readiness section so automated review checks the PR before diving into code.Reviewers (and Bugbot) are told to flag oversized or mixed-concern diffs (e.g. ~400-line ideal, one component per PR, isolated token cascades), thin descriptions (what / why / how verified, including AI boilerplate), and changeset level vs. actual API impact, as top-level comments—not inline nits.
A new automated checks table maps CI signals (PR comment bot, story coverage, export/publint/attw, Storybook axe, Chromatic, package size) and says to flag when failures aren’t explained in the description. A horizontal rule separates this block from the existing “What to focus on” review priorities.
Reviewed by Cursor Bugbot for commit 90831b4. Bugbot is set up for automated code reviews on this repo. Configure here.