@@ -663,12 +663,17 @@ practices detailed in `AGENTS.md`.
663663 to locate files/modules based on common directory structures are
664664 unsuccessful, explicitly ask for more specific paths rather than assuming a
665665 module doesn't exist or contains no relevant code.
666- * ** GitHub PR Review Comments** : If the user asks you to address comments from
667- GitHub code review, that means that you should run the following command:
668- ` python3 scripts/print_github_reviews.py --branch BRANCH_NAME_THAT_JULES_PUSHED_TO_GITHUB `
669- (with the remote branch name that was actually pushed to GitHub substituted,
670- and if you aren't sure what it is or it returns an error, just ask the user,
671- as they may have renamed the branch before pushing) and address the comments
672- it shows. If it succeeds, then subsequent times you run the script on the
673- same branch, include the ` --since ` parameter in accordance with the previous
674- script run's output to ensure you only fetch new comments.
666+
667+ ## GitHub Code Review Comments -- IMPORTANT, JULES READ THIS SECTION
668+
669+ If the user asks you to look at GitHub code review comments, PR reviews, etc,
670+ that means that you should run the following command:
671+
672+ ` python3 scripts/print_github_reviews.py --branch BRANCH_NAME_THAT_JULES_PUSHED_TO_GITHUB `
673+
674+ (with the remote branch name that was actually pushed to GitHub substituted, and
675+ if you aren't sure what it is or it returns an error, just ask the user, as they
676+ may have renamed the branch before pushing) and then address the comments that
677+ the output shows. If it succeeds, then subsequent times you run the script on
678+ the same branch, include the ` --since ` parameter in accordance with the previous
679+ script run's output to ensure you only fetch new comments.
0 commit comments