fix: update review effort label format to use X/5 notation

[mrT23]

PR Type

Bug fix

---

Description

• Updated review effort label format to X/5 notation.

• Ensured consistent formatting for review effort labels.

---

Changes walkthrough 📝

	Relevant files
Bug fix	pr_reviewer.py Update review effort label format to `X/5`                              pr_agent/tools/pr_reviewer.py Changed review effort label format from [1-5]: X to X/5. Improved clarity and consistency in label representation. +1/-1

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

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

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

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

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Add missing None check Add input validation to ensure estimated_effort_number is not None before the comparison, as the code assumes it exists but doesn't verify it. pr_agent/tools/pr_reviewer.py [373-374] -if 1 <= estimated_effort_number <= 5: # 1, because ... +if estimated_effort_number is not None and 1 <= estimated_effort_number <= 5: # 1, because ... review_labels.append(f'Review effort {estimated_effort_number}/5') [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 8 __ Why: The suggestion addresses a potential runtime error by adding a crucial None check before accessing estimated_effort_number. This is important as the variable could be None if none of the previous conditions set its value, which would cause a TypeError.	Medium
Learned best practice	Add defensive programming practices by including null checks and standardizing boolean parsing from strings Add null check for security_concerns before performing string operations to prevent potential NullPointerException. Also consider using a helper function to standardize the boolean parsing logic. pr_agent/tools/pr_reviewer.py [376-377] -security_concerns = data['review']['security_concerns'] # yes, because ... -security_concerns_bool = 'yes' in security_concerns.lower() or 'true' in security_concerns.lower() +security_concerns = data.get('review', {}).get('security_concerns', '') +security_concerns_bool = any(val in security_concerns.lower() for val in ['yes', 'true']) if security_concerns else False [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 6	Low

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