Remove suggestion blocks from prompt #6
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Switching from GitHub suggestion blocks to plain fenced code blocks is a good simplification and the guidance reads clearly. I left one small consistency suggestion about straight vs. curly quotes in a template line.
🤖 Automated review complete. Please react with 👍 or 👎 on the individual review comments to provide feedback on their usefulness.
| - **HIGH CONFIDENCE ONLY**: Only suggest changes you are highly confident will improve the code | ||
| - Post one inline comment per distinct issue and location, anchored to the exact file and line in the PR diff | ||
| - Provide clear explanations of issues and suggest concrete improvements; when proposing code, use GitHub suggestion blocks in inline comments | ||
| - Provide clear explanations of issues and suggest concrete improvements. When proposing code, do NOT use GitHub suggestion blocks. Instead, include regular fenced code blocks with appropriate language tags and, where useful, show “Current code:” and “Suggested improvement:” sections |
Contributor
There was a problem hiding this comment.
Suggestion: Use straight quotes instead of curly quotes around the section labels to be consistent with the other templates in this PR and avoid potential copy/paste or rendering inconsistencies.
Current code:
... include regular fenced code blocks with appropriate language tags and, where useful, show “Current code:” and “Suggested improvement:” sectionsSuggested improvement:
... include regular fenced code blocks with appropriate language tags and, where useful, show "Current code:" and "Suggested improvement:" sections
justinxu421
approved these changes
Sep 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove GitHub suggestion blocks from review prompts and replace with fenced code blocks
This PR updates the review prompt templates to stop using GitHub suggestion blocks and instead rely on regular fenced code blocks for proposed changes. This avoids incorrect/mishandled suggestions and makes before/after examples clearer and more consistent.
Key changes:
Impact:
🤖 This description was generated automatically. Please react with 👍 if it's helpful or 👎 if it needs improvement.