# Cursor Looking at Git PR

**URL:** <https://forum.cursor.com/t/cursor-looking-at-git-pr/7783>\
**Category:** Discussions\
**Created:** [August 19, 2024, 7:01am UTC](https://forum.cursor.com/t/cursor-looking-at-git-pr/7783 "2024-08-19T07:01:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Spark](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/spark/32/4126_2.png) [@Spark](https://forum.cursor.com/u/Spark)\
**Post date:** [January 11, 2025, 12:33pm UTC](https://forum.cursor.com/t/cursor-looking-at-git-pr/7783/2 "2025-01-11T12:33:49Z")

</div>

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:

```auto
@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.

```

---

_[View the full topic](https://forum.cursor.com/t/cursor-looking-at-git-pr/7783)._