Cursor Looking at Git PR

Discussions
1

I already have a large codebase where we regularly perform pull requests (PRs). What’s the simplest way to ask Cursor how to review a PR in the context of the main branch? Would it be sufficient to just copy and paste the changes exported from Git or is there a cleaner way?

2

I was looking for the same thing and was bout to build a pipeline for PR review, but that is actually not necessary. In Cursor Chat, you can use @PR to reference it and add some instructions that serve your needs.
Here’s how I do it:

@PR (Diff with Main Branch) 
Please analyze the code changes and provide the following information:

1. **Intent and Purpose**: Summarize the goal of the changes. Explain what functionality or behavior the changes aim to introduce, modify, or fix.

2. **Potential Issues**: Identify any possible problems the changes might introduce, such as:
   - Bugs or unintended side effects.
   - Performance concerns.
   - Code quality issues (e.g., readability, maintainability, scalability).
   - Violations of best practices or standards.

3. **Suggestions for Improvement**: Recommend any improvements or alternative approaches that could enhance the code.
3

@Spark how can I find out more about @PR

4

@codekiln What do you need to know? @PR (Diff with Main Branch) is simply adding the git diff as your reference. You can achieve the same thing by streaming your diff into a file an use this as a reference for cursor. This way you can even compare to other branches than your master.

git diff origin/master > diff.txt

1 Like
5

Hi there, @PR is great but could be great instead to have the possibility to analyze remote PR opened by someone else that are not pointing to the main branch. Do you see feasible?

1 Like
6

i think this should be possible with the GitHub MCP server

7

Hi, im looking for some extension to review the PR’s in Cursor but GitHub Pull Requests is not working for me in Cursor, which tool do you use? :sad_but_relieved_face:

8

Where the heck is the library (not a lib - but directory SHHHH)

of MCPs and how call…

We should be able to @ call MCPs and throw|pipe between them by now

TAKE SUCH and | @BLAH(from_the_library) → | @MCP_OTHER_BLAH and give me XYZ as a single, cheap token call both internally/ext

(naybe an MCP call needs its own hook… such as a [1] nomenclature?

  1. MCP_library_call ↩︎