refine help

[mrT23]

Type

enhancement, documentation

---

Description

• Enhanced help message readability by aligning tables to the left and simplifying tool descriptions.
• Introduced new tools (IMPROVE COMPONENT, ANALYZE, ASK, GENERATE CUSTOM LABELS) to the help message, expanding the functionality offered to users.
• Updated tool names for consistency (ADD DOCS instead of ADD DOCUMENTATION) and clarity.
• Simplified the invocation process for tools, making it easier for users to understand how to use them.

---

Changes walkthrough

Relevant files

Enhancement

pr_help_message.py Enhance Help Message and Add New Tools                                      pr_agent/tools/pr_help_message.py Updated tool names and descriptions for clarity and consistency. Added new tools (IMPROVE COMPONENT, ANALYZE, ASK, GENERATE CUSTOM LABELS) to the help message. Modified table alignment from center to left for better readability. Simplified descriptions and commands for invoking tools. +27/-20

---

✨ PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-merge-pro]

PR Description updated to latest commit (c3b3651)

• Copy walkthrough table to "Files Changed" Tab

[qodo-merge-pro]

PR Review

⏱️ Estimated effort to review [1-5]	2, because the changes are mostly textual updates and reordering of elements within the code, which are straightforward to review. The complexity is low, and the main focus would be on ensuring that the textual changes are accurate and improve clarity as intended.
🏅 Score	85
🧪 Relevant tests	No
🔍 Possible issues	Consistency in Tool Naming: The renaming of tools for consistency is a positive change, but it's essential to ensure that all references to these tools elsewhere in the documentation or codebase are also updated to prevent confusion.
	Command Invocation Clarity: The simplification of commands and descriptions is beneficial for user experience. However, it's crucial to verify that these changes do not omit necessary details that users might need to understand how to use the tools effectively.
🔒 Security concerns	No
🔀 Multiple PR themes	No

---

✨ Review tool usage guide:

---

Overview:
The review tool scans the PR code changes, and generates a PR review which includes several types of feedbacks, such as possible PR issues, security threats and relevant test in the PR. More feedbacks can be added by configuring the tool.

The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.

• When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

• With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

See the review usage page for a comprehensive guide on using this tool.

[qodo-merge-pro]

PR Code Suggestions

Category	Suggestions
Maintainability	Use a loop to append multiple items to lists to reduce code redundancy. Consider using a loop to append items to tool_names, descriptions, and commands lists to reduce redundancy and improve maintainability. pr_agent/tools/pr_help_message.py [31-36] -tool_names.append(f"[ADD DOCS]({base_path}/documentation/) 💎") -tool_names.append(f"[TEST]({base_path}/test/) 💎") -tool_names.append(f"[IMPROVE COMPONENT]({base_path}/improve_component/) 💎") -tool_names.append(f"[ANALYZE]({base_path}/analyze/) 💎") -tool_names.append(f"[ASK]({base_path}/ask/)") -tool_names.append(f"[GENERATE CUSTOM LABELS]({base_path}/custom_labels/) 💎") +tools = [("ADD DOCS", "documentation"), ("TEST", "test"), ("IMPROVE COMPONENT", "improve_component"), ("ANALYZE", "analyze"), ("ASK", "ask"), ("GENERATE CUSTOM LABELS", "custom_labels")] +for tool_name, path in tools: + tool_names.append(f"[{tool_name}]({base_path}/{path}/) 💎")
	Remove redundant placeholder checkboxes to clean up the list. Remove the redundant placeholder checkboxes "[*]" to clean up the checkbox list and avoid confusion. pr_agent/tools/pr_help_message.py [80-81] -checkbox_list.append("[*]") -checkbox_list.append("[*]") +# These lines are removed to clean up the checkbox list
Enhancement	Use a dictionary to map tool names to their descriptions and commands for consistency and maintainability. To ensure consistency and avoid potential errors, consider using a dictionary to map tool names to their descriptions and commands, then iterate over this dictionary to populate tool_names, descriptions, and commands. pr_agent/tools/pr_help_message.py [42-54] -descriptions.append("Generates PR description - title, type, summary, code walkthrough and labels") -descriptions.append("Adjustable feedback about the PR, possible issues, security concerns, review effort and more") -descriptions.append("Code suggestions for improving the PR") -descriptions.append("Automatically updates the changelog") -descriptions.append("Generates documentation to methods/functions/classes that changed in the PR") -descriptions.append("Generates unit tests for a specific component, based on the PR code change") -descriptions.append("Code suggestions for a specific component that changed in the PR") -descriptions.append("Identifies code components that changed in the PR, and enables to interactively generate tests, docs, and code suggestions for each component") -descriptions.append("Answering free-text questions about the PR") -descriptions.append("Generates custom labels for the PR, based on specific guidelines defined by the user") -descriptions.append("Generates feedback and analysis for a failed CI job") -descriptions.append("Generates custom suggestions for improving the PR code, based only on specific guidelines defined by the user") -descriptions.append("Automatically retrieves and presents similar issues") +tools_info = { + "DESCRIBE": ("Generates PR description - title, type, summary, code walkthrough and labels", "/describe"), + "REVIEW": ("Adjustable feedback about the PR, possible issues, security concerns, review effort and more", "/review"), + ... +} +for tool, (desc, cmd) in tools_info.items(): + descriptions.append(desc) + commands.append(f"`/{cmd}`")
	Align table contents to the center for better readability. Align the table headers and cell contents to the center for better readability and consistency with the rest of the documentation. pr_agent/tools/pr_help_message.py [90-92] -pr_comment += f"<table><tr align='left'><th align='left'>Tool</th><th align='left'>Description</th><th align='left'>Trigger Interactively :gem:</th></tr>" -pr_comment += f"\n<tr><td align='left'>\n\n<strong>{tool_names[i]}</strong></td>\n<td>{descriptions[i]}</td>\n<td>\n\n{checkbox_list[i]}\n</td></tr>" +pr_comment += f"<table><tr align='center'><th align='center'>Tool</th><th align='center'>Description</th><th align='center'>Trigger Interactively :gem:</th></tr>" +pr_comment += f"\n<tr><td align='center'>\n\n<strong>{tool_names[i]}</strong></td>\n<td align='center'>{descriptions[i]}</td>\n<td align='center'>\n\n{checkbox_list[i]}\n</td></tr>"
Possible issue	Ensure lists have the same length to avoid index errors. Ensure that the number of elements in tool_names, descriptions, and commands lists are the same to avoid index out of range errors when iterating over them. pr_agent/tools/pr_help_message.py [91-92] +assert len(tool_names) == len(descriptions) == len(commands), "Lists tool_names, descriptions, and commands must have the same length" for i in range(len(tool_names)): pr_comment += f"\n<tr><td align='left'>\n\n<strong>{tool_names[i]}</strong></td>\n<td>{descriptions[i]}</td>\n<td>\n\n{checkbox_list[i]}\n</td></tr>"

---

✨ Improve tool usage guide:

---

Overview:
The improve tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.

• When commenting, to edit configurations related to the improve tool (pr_code_suggestions section), use the following template:

/improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=...

• With a configuration file, use the following template:

[pr_code_suggestions]
some_config1=...
some_config2=...

See the improve usage page for a comprehensive guide on using this tool.