refactor: remove legacy code suggestions feature from review tool

[mrT23]

User description

#1415

---

PR Type

Enhancement

---

Description

• Removed the legacy code suggestions feature from the review tool, as it has been replaced by the improve tool
• Removed configuration options related to code suggestions:
  • num_code_suggestions
  • inline_code_comments
  • ask_and_reflect
• Updated documentation to reflect these changes and direct users to use the improve tool instead
• Removed code feedback processing and markdown conversion functionality
• Updated tests to remove code suggestions related test cases
• Cleaned up configuration files and review prompts

---

Changes walkthrough 📝

	Relevant files
Enhancement	pr_agent.py Remove reflect and review configuration                                    pr_agent/agent/pr_agent.py Removed code related to reflect_and_review action +0/-2      utils.py Remove code feedback markdown conversion                                  pr_agent/algo/utils.py Removed code_feedback section from markdown conversion +0/-16    pr_reviewer.py Remove code suggestions and inline comments functionality pr_agent/tools/pr_reviewer.py Removed num_code_suggestions configuration Removed inline code comments functionality Removed code feedback processing and publishing +0/-62
Tests	test_convert_to_markdown.py Update tests to remove code feedback assertions                    tests/unittest/test_convert_to_markdown.py Updated tests to remove code_feedback related test cases +3/-6
Documentation	review.md Update documentation to remove code suggestions feature    docs/docs/tools/review.md Removed documentation for num_code_suggestions and inline_code_comments Updated documentation to reflect removal of code suggestions feature +5/-17    automations_and_usage.md Update automation examples for code suggestions removal    docs/docs/usage-guide/automations_and_usage.md Updated example configuration to remove num_code_suggestions parameter +1/-1
Configuration changes	configuration.toml Remove legacy code suggestions configuration                          pr_agent/settings/configuration.toml Removed legacy configuration options for code suggestions +0/-3      pr_reviewer_prompts.toml Remove code suggestions from review prompts                            pr_agent/settings/pr_reviewer_prompts.toml Removed code suggestions related prompts and model definitions +0/-42

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 1415 - Fully compliant Compliant requirements: Remove legacy code suggestions feature from review tool Remove configuration options: num_code_suggestions, inline_code_comments, ask_and_reflect Update documentation to reflect changes and direct users to use improve tool Remove code feedback processing and markdown conversion functionality Update tests to remove code suggestions test cases Clean up configuration files and review prompts

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🏅 Score: 95

🧪 PR contains tests

🔒 No security concerns identified

⚡ No major issues detected

[mrT23]

/improve

[qodo-merge-pro-for-open-source]

PR Code Suggestions ✨

Latest suggestions up to 83e68f1

Category	Suggestion	Score
General	Enhance error logging to provide more context about failed operations Add error handling or logging details about why the command failed. Simply logging "Unknown command" provides limited debugging information. pr_agent/agent/pr_agent.py [75-77] if action not in command2class: - get_logger().error(f"Unknown command: {action}") + get_logger().error(f"Unknown command '{action}'. Valid commands are: {list(command2class.keys())}") return False Apply this suggestion Suggestion importance[1-10]: 6 Why: The suggestion improves error logging by adding the list of valid commands, which helps users quickly identify and fix command usage issues. This is a meaningful improvement for debugging and user experience.	6

• Author self-review: I have reviewed the PR code suggestions, and addressed the relevant ones.

---

Previous suggestions

✅ Suggestions up to commit 495c1eb

Category	Suggestion	Score
General	✅ Improve error logging for better debugging and monitoring of unknown commands Suggestion Impact: Changed the log level from debug to error when encountering unknown commands, exactly as suggested code diff: - get_logger().debug(f"Unknown command: {action}") + get_logger().error(f"Unknown command: {action}") Add error handling or logging when an unknown command is encountered to help with debugging and monitoring. pr_agent/agent/pr_agent.py [78-80] if action not in command2class: - get_logger().debug(f"Unknown command: {action}") + get_logger().error(f"Unknown command: {action}") return False Suggestion importance[1-10]: 3 Why: While the suggestion to change debug to error level logging is valid, it's a minor improvement as the current debug logging is already sufficient for tracking unknown commands.	3
Possible issue	Simplify null check and prevent potential NoneType errors Add error handling for the case when markdown_text is None to avoid potential NoneType errors. pr_agent/tools/pr_reviewer.py [260-261] -if markdown_text == None or len(markdown_text) == 0: +if not markdown_text: markdown_text = "" Suggestion importance[1-10]: 2 Why: The suggestion to use 'if not markdown_text' is a minor style improvement. The existing code is already safe and handles None values correctly.	2