refactor: remove legacy code suggestions feature from review tool

pr_agent/settings/configuration.toml

@@ -55,9 +55,6 @@ require_can_be_split_review=false
 require_security_review=true
 require_ticket_analysis_review=true
 # general options
-num_code_suggestions=0 # legacy mode. use the `improve` command instead
-inline_code_comments = false
-ask_and_reflect=false
 persistent_comment=true
 extra_instructions = ""
 final_update_message = true

pr_agent/settings/pr_reviewer_prompts.toml

@@ -1,10 +1,6 @@
 [pr_review_prompt]
 system="""You are PR-Reviewer, a language model designed to review a Git Pull Request (PR).
-{%- if num_code_suggestions > 0 %}
-Your task is to provide constructive and concise feedback for the PR, and also provide meaningful code suggestions.
-{%- else %}
 Your task is to provide constructive and concise feedback for the PR.
-{%- endif %}
 The review should focus on new code added in the PR code diff (lines starting with '+')
 
 
@@ -49,16 +45,6 @@ __new hunk__
 {%- endif %}
 - When quoting variables or names from the code, use backticks (`) instead of single quote (').
 
-{%- if num_code_suggestions > 0 %}
-
-
-Code suggestions guidelines:
-- Provide up to {{ num_code_suggestions }} code suggestions. Try to provide diverse and insightful suggestions.
-- Focus on important suggestions like fixing code problems, issues and bugs. As a second priority, provide suggestions for meaningful code improvements, like performance, vulnerability, modularity, and best practices.
-- Avoid making suggestions that have already been implemented in the PR code. For example, if you want to add logs, or change a variable to const, or anything else, make sure it isn't already in the PR code.
-- Don't suggest to add docstring, type hints, or comments.
-- Suggestions should address the new code added in the PR diff (lines starting with '+')
-{%- endif %}
 
 {%- if extra_instructions %}
 
@@ -118,25 +104,9 @@ class Review(BaseModel):
 {%- if require_can_be_split_review %}
     can_be_split: List[SubPR] = Field(min_items=0, max_items=3, description="Can this PR, which contains {{ num_pr_files }} changed files in total, be divided into smaller sub-PRs with distinct tasks that can be reviewed and merged independently, regardless of the order ? Make sure that the sub-PRs are indeed independent, with no code dependencies between them, and that each sub-PR represent a meaningful independent task. Output an empty list if the PR code does not need to be split.")
 {%- endif %}
-{%- if num_code_suggestions > 0 %}
-
-class CodeSuggestion(BaseModel):
-    relevant_file: str = Field(description="The full file path of the relevant file")
-    language: str = Field(description="The programming language of the relevant file")
-    suggestion: str = Field(description="a concrete suggestion for meaningfully improving the new PR code. Also describe how, specifically, the suggestion can be applied to new PR code. Add tags with importance measure that matches each suggestion ('important' or 'medium'). Do not make suggestions for updating or adding docstrings, renaming PR title and description, or linter like.")
-    relevant_line: str = Field(description="a single code line taken from the relevant file, to which the suggestion applies. The code line should start with a '+'. Make sure to output the line exactly as it appears in the relevant file")
-{%- endif %}
-{%- if num_code_suggestions > 0 %}
 
 class PRReview(BaseModel):
     review: Review
-    code_feedback: List[CodeSuggestion]
-{%- else %}
-
-
-class PRReview(BaseModel):
-    review: Review
-{%- endif %}
 =====
 
 
@@ -185,18 +155,6 @@ review:
     title: ...
   - ...
 {%- endif %}
-
-{%- if num_code_suggestions > 0 %}
-code_feedback:
-- relevant_file: |
-    directory/xxx.py
-  language: |
-    python
-  suggestion: |
-    xxx [important]
-  relevant_line: |
-    xxx
-{%- endif %}
 ```
 
 Answer should be a valid YAML, and nothing else. Each YAML output MUST be after a newline, with proper indent, and block scalar indicator ('|')