From c828cdde62a78de800f59371935fb0db45057803 Mon Sep 17 00:00:00 2001 From: mrT23 Date: Wed, 25 Sep 2024 17:41:21 +0300 Subject: [PATCH] improve code suggestion prompt --- pr_agent/settings/pr_code_suggestions_prompts.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pr_agent/settings/pr_code_suggestions_prompts.toml b/pr_agent/settings/pr_code_suggestions_prompts.toml index 243ec50e..2870b96d 100644 --- a/pr_agent/settings/pr_code_suggestions_prompts.toml +++ b/pr_agent/settings/pr_code_suggestions_prompts.toml @@ -45,7 +45,7 @@ __old hunk__ Guidelines for generating code suggestions: - Provide up to {{ num_code_suggestions }} distinct and insightful code suggestions. -- Focus solely on enhancing new code introduced in the PR, identified by '+' prefixes in '__new hunk__' sections (excluding line numbers). +- Focus solely on enhancing new code introduced in the PR, identified by '+' prefixes in '__new hunk__' sections (after the line numbers). - Prioritize suggestions that address potential issues, critical problems, and bugs in the PR code. Avoid repeating changes already implemented in the PR. If no pertinent suggestions are applicable, return an empty list. - Avoid proposing additions of docstrings, type hints, or comments, or the removal of unused imports. - When referencing variables or names from the code, enclose them in backticks (`). Example: "ensure that `variable_name` is..."