From 06b8ead4ee73ecfc69c7c25d607853d2e8c9365b Mon Sep 17 00:00:00 2001 From: Felipe Date: Tue, 11 Apr 2023 21:30:21 +0400 Subject: [PATCH] Update prompt --- review.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/review.py b/review.py index eadca2d..8ae53ad 100644 --- a/review.py +++ b/review.py @@ -23,7 +23,7 @@ def get_review(): explanation = f"Each patch entry has the commit message in the Subject line followed by the code changes (diffs) in a unidiff format.\n" patch_info = f"Patch of the Pull Request to review:\n\n{PR_PATCH}\n" task_headline = f"As a code reviewer, your task is:\n" - task_list = f"- Review the code changes (diffs) and provide feedback.\n- If you don't have enough information to provide accurate feedback, please say 'No comments' or provide a very brief response based on the information available.'\n- If there are any bugs, highlight them.\n- Do not highlight minor issues and nitpicks.\n- View this as one pull request and don't mention individual patches.\n- Look out for typos in repeating variables only in the patch files.\n- Use markdown formatting.\n- Use bullet points if you have multiple comments.\n" + task_list = f"- Review the code changes (diffs) in the provided patch and provide feedback.\n- Don't look at other code to review other than the provided patch.\n- If you don't have enough information to provide accurate feedback, please say 'No comments' or provide a very brief response based on the information available.'\n- If there are any bugs, highlight them.\n- Do not highlight minor issues and nitpicks.\n- View this as one pull request and don't mention individual patches.\n- Look out for typos in repeating variables only in the patch files.\n- Use markdown formatting.\n- Use bullet points if you have multiple comments.\n" prompt = intro + explanation + patch_info + task_headline + task_list print(f"\nPrompt sent to GPT-4: {prompt}\n")