Enable RAG on relevant repos

[kdvalin]

User description

Description

Enables RAG parsing for Qodo on test_tools-wrappers and pyperf-wrapper to bring relevant context to the bot's reviews.

Before/After Comparison

Before

Qodo would only have the context of this repo, and will not know anything about the tools in the test_tools-wrappers repo.

After

Qodo will have both this repo and test_tools-wrappers in it's context to perform code feedback.

Clerical Stuff

This closes #64
Relates to JIRA: RPOPC-830

---

PR Type

Enhancement

---

Description

• Added RAG configuration file for AI code review

• Enabled RAG parsing for two related repositories

• Configured context from test_tools-wrappers and pyperf-wrapper repos

---

Diagram Walkthrough

flowchart LR
  A["New .pr_agent.toml"] --> B["Enable RAG"]
  B --> C["Add test_tools-wrappers repo"]
  B --> D["Add pyperf-wrapper repo"]

Loading

File Walkthrough

	Relevant files
Configuration changes	.pr_agent.toml Configure RAG with external repository references                .pr_agent.toml Created new configuration file for PR agent Enabled RAG (Retrieval-Augmented Generation) feature Added two external repositories to RAG context: test_tools-wrappers and pyperf-wrapper +6/-0

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	External context access Description: Enabling RAG and adding external repositories to rag_repo_list may cause unintended data exposure (e.g., the PR agent fetching/embedding code or files from redhat-performance/test_tools-wrappers and redhat-performance/pyperf-wrapper into prompts/logs), so access controls, data retention, and repository sensitivity/licensing should be verified. .pr_agent.toml [1-6] Referred Code [rag_arguments] enable_rag=true rag_repo_list= [ "redhat-performance/test_tools-wrappers", "redhat-performance/pyperf-wrapper" ]
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[github-actions]

This relates to RPOPC-830

[frival]

LGTM