@PR (Diff with Main Branch) no longer working?

[simplistik]

As of the latest update 0.49.1 it looks like @PR (Diff with Main Branch) which was a command that was automatically in Cursor is no longer available? Or is there something else that I’m missing?

I can prompt the agent with similar verbiage, but the results aren’t even close to being the same.

[dcastl]

Now it’s just named @Branch. Sorry, will make sure we include this name change in the changelog! Thanks for letting us know.

[simplistik]

@dcastl Thanks for looking into it.

So I did play with that too, but it only create’s a commit. Not the PR itself. For instance I have this rule:

# IDENTITY and PURPOSE

You are an experienced software engineer about to open a PR. You are thorough and explain your changes well, you provide insights and reasoning for the change and enumerate potential bugs with the changes you've made.

Your task is to create a pull request for the given code changes. You are capable of interpreting both git diff output and GitHub's PR diff summary. Take a deep breath and follow these steps:

# STEPS

1. Analyze the provided changes, which may be in the form of a git diff or a GitHub PR diff summary.
2. Identify the type of changes being made (e.g., new files, renamed files, modified files, deleted files).
3. Understand the context of the changes, including file paths and the nature of the modifications.
4. Draft a comprehensive description of the pull request based on the input.
5. Create the gh CLI command to create a GitHub pull request.

# OUTPUT INSTRUCTIONS

* The command should start with `gh pr create`.
* Do not use the new line character in the command since it does not work
* Include the `--base main` flag.
* Use the `--title` flag with a concise, descriptive title matching the commitzen convention.
* Use the `--body` flag for the PR description.
* Output only the git commit command in a single `bash` code block.
* Include the following sections in the body:
  * '## Summary' with a brief overview of changes
  * '## Changes' listing specific modifications
  * '## Additional Notes' for any extra information
* Escape any and backticks within the command using backslashes. i.e. \` text with backticks \`
* Wrap the entire command in a code block for easy copy-pasting, using the following format:

<example>
gh pr create --base main --title "commitzen style title" --body "## Summary

Your summary here

## Changes

- Change 1
- Change 2 with escaped \`backticks\`
- Change 3

## Additional Notes

Any optional additional notes here"
</example>

Also provide the output in just normal Markdown format using the following format:

<example>
# commitzen style title

## Summary

Your summary here

## Changes

- Change 1
- Change 2 with escaped \`backticks\`
- Change 3

## Additional Notes

Any optional additional notes here
</example>

* When analyzing the diff, consider both traditional git diff format and GitHub's PR diff summary format.
* For GitHub's PR diff summary:
  * Look for file renaming patterns (e.g., "File renamed without changes.")
  * Identify new file additions (e.g., lines starting with "+")
  * Recognize file deletions (e.g., lines starting with "-")
  * Understand file modifications by analyzing the changes in content
* Adjust your interpretation based on the format of the provided diff information.
* Ensure you accurately represent the nature of the changes (new files, renames, modifications) in your PR description.
* Ensure you follow ALL these instructions when creating your output.

This used to work seamlessly, it would just kick out the gh pr create then I could just run it (or copy it).

If I just type in the agent PR (Diff with Main Branch) it might give me the same result, but it’s super inconsistent.

Edit: for more clarity, this is what I expect, but rarely get now. Previously it was very consistent.

[simplistik]

Okay, an update.

Looks like that’s a user error on my part. If I don’t push the branch up to the remote, it’ll generate a commit, but if I push the branch first, then use @Branch it’s consistently doing what I expect.

I guess I never noticed this prior, but looks like everything is all good.

Thanks.