Bugbot like PR reviewer

Support Help
, ,
1

hy,

we have cursor subscription and have bugbot running, which is working nicely and don’t want to modify it.

however, we have a use case, where we want another - similar agent like bugbot - running on PRs to review changes, interpret them and make suggestions on the github PR to the corresponding documentation along some predefined guidelines.

the documentation exists in a separate file and doesn’t live in the codebase, but its location is deterministic - think of it like a glossary

do you maybe have a recommendation of what approaches i have using cursor?

thank you!

4

run cursor cli on a github action with your preferred model

2 Likes
5

Hey there!

If you want to keep BugBot running exactly as-is for bug detection, the cleanest approach is Cursor Automations. It’s a separate system from BugBot, so you can add a docs-review workflow without the two stepping on each other.

Here’s a good setup:

  • Create a new automation at cursor.com/automations/new

  • Set the trigger to PR events for your repo (opened + updated / synchronize)

  • Add a prompt that includes your documentation review guidelines: what to scan for in the diff, what “good” looks like, and how to map changes to your glossary/terminology

  • The automation runs as a Cloud Agent and can post review comments directly on the PR

Because your glossary/docs live outside the codebase, you’ll want to make them available to the agent. In the automation config, you can add tools (via MCP servers) depending on where the source of truth lives—for example:

  • GitHub MCP (if the glossary is in another repo)

  • Notion / Confluence MCP (if it’s in your docs workspace)

  • A generic fetch/read tool (if it’s hosted somewhere accessible)

You can also browse the Automations marketplace/templates for examples of PR-triggered review workflows.

One alternative is running the Cursor CLI inside a GitHub Action for maximum control. That can work well, but it usually means more CI/auth wiring and ongoing maintenance. Automations tends to be simpler if you want the “native” version of this flow.

If you run into any rough edges while setting it up, send over what you’re trying (trigger + prompt + where the glossary lives) and I’ll help you tighten it up.

Best,
Mohit

1 Like