2 min lesson
Review the finding
Classify one finding, verify its behavior and complete a human review of the latest pull request diff.
Check your understanding
Complete the practice "Classify one Bugbot finding before merge".
Outcome: The confirmed defect blocked until fixed. The style note stayed advisory, and the service owner resolved the architecture question.
Classify one Bugbot finding before merge
Latest commit, reproduction, repository rule, human review
SayBugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. reported a possible SQL injection and suggested a variable rename on the current payments pull request. Which one can stop the merge?
DoOpen the SQL finding on the latest commit and run the focused test with a quoted input.
SeeThe test reproduces the defect. The repository rule requires security defects to be resolved, so request changes until the code and test pass.
DoOpen the rename suggestion and compare it with the repository's review rules.
SeeThe name is clear and no rule requires the change. Leave the suggestion advisory or dismiss it with that reason.
SayThe agent also asks whether the query belongs in the payments service.
DoAsk the service owner to resolve that architecture question in the pull request thread.
SeeThe agent can explain the diff, but the owning team decides the service boundary.
DoRead the full diff, checks and unresolved threads. After the SQL fix passes its test and a new review covers the latest commit, make the human review decision.
SeeThe confirmed defect blocked until fixed. The style note stayed advisory, and the service owner resolved the architecture question.
Learn more
Optional practice
Test yourself on Review the finding
QWhich result proves the finding and pull request are ready for a human review decision?