docs: update pr_help_prompts.toml with project name change and format…

[mrT23]

User description

…ting adjustments

---

PR Type

Documentation

---

Description

• Updated the project name in the pr_help_prompts.toml file from "PR-Agent" to "Qodo Merge" to reflect the recent renaming.
• Made formatting adjustments in the YAML example output section to improve consistency and readability.

---

Changes walkthrough 📝

	Relevant files
Documentation	pr_help_prompts.toml Update project name and adjust formatting in TOML file      pr_agent/settings/pr_help_prompts.toml Updated project name from "PR-Agent" to "Qodo Merge". Corrected formatting in YAML example output. +6/-6

---

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

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🏅 Score: 95

🧪 No relevant tests

🔒 No security concerns identified

🔀 No multiple PR themes

⚡ Recommended focus areas for review Inconsistent Naming The project name is inconsistently referred to as both "PR-Agent" and "Qodo Merge" in the updated text. This should be standardized to avoid confusion.

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Best practice	Correct spelling errors to maintain the quality of the documentation Correct the spelling of "open-soure" to "open-source" to maintain professionalism in the documentation. pr_agent/settings/pr_help_prompts.toml [2] -You are Doc-helper, a language models designed to answer questions about a documentation website for an open-soure project called "PR-Agent" (recently renamed to "Qodo Merge"). +You are Doc-helper, a language model designed to answer questions about a documentation website for an open-source project called "Qodo Merge" (recently renamed from "PR-Agent"). Apply this suggestion Suggestion importance[1-10]: 9 Why: Correcting the spelling error from "open-soure" to "open-source" is essential for maintaining professionalism and accuracy in the documentation. This correction is straightforward and significantly improves the document's quality.	9
Maintainability	Ensure consistent use of the new project name throughout the documentation Consider updating the project name consistently throughout the file. While the change from "PR-Agent" to "Qodo Merge" is mentioned, the reference to 'pr-agent' in line 9 remains unchanged. pr_agent/settings/pr_help_prompts.toml [9] -- The main tools of PR-Agent are 'describe', 'review', 'improve'. If there is ambiguity to which tool the user is referring to, prioritize snippets of these tools over others. +- The main tools of Qodo Merge are 'describe', 'review', 'improve'. If there is ambiguity to which tool the user is referring to, prioritize snippets of these tools over others. Apply this suggestion Suggestion importance[1-10]: 8 Why: The suggestion correctly identifies an inconsistency in the project name update, which is crucial for maintaining clarity and consistency in the documentation. This change enhances the maintainability and professionalism of the document.	8
Enhancement	Provide context for the project's name change to help users understand the transition Consider adding a brief explanation about the recent name change from "PR-Agent" to "Qodo Merge" to provide context for users who might be familiar with the old name. pr_agent/settings/pr_help_prompts.toml [2] -You are Doc-helper, a language models designed to answer questions about a documentation website for an open-soure project called "PR-Agent" (recently renamed to "Qodo Merge"). +You are Doc-helper, a language model designed to answer questions about a documentation website for an open-source project called "Qodo Merge" (formerly known as "PR-Agent"). The project was recently renamed to reflect its evolving scope and capabilities. Apply this suggestion Suggestion importance[1-10]: 7 Why: Adding context about the name change can help users who are familiar with the old name understand the transition, improving user experience and clarity. However, this is more of an enhancement than a critical fix.	7

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

💡 Need additional feedback ? start a PR chat