Add PR analysis with code context investigation#95
Open
mohit-sheth wants to merge 1 commit intoredhat-performance:mainfrom
Open
Add PR analysis with code context investigation#95mohit-sheth wants to merge 1 commit intoredhat-performance:mainfrom
mohit-sheth wants to merge 1 commit intoredhat-performance:mainfrom
Conversation
Add 9 GitHub investigation tools (pr_tools.py) that let the LLM autonomously explore PR diffs, commits, file contents, and metadata during regression analysis. Integrate tools with MCP/Orion tools in pr_analyzer.py. Update prompts with funnel investigation strategy (scope assessment, adaptive small/large PR handling, subsystem mapping), lower severity thresholds to 8%, and add test file exclusion guardrails. Includes developer documentation at docs/enhancement-pr-analysis.md. Signed-off-by: Mohit Sheth <msheth@redhat.com>
| # ============================================================================= | ||
|
|
||
|
|
||
| def create_pr_tools(org: str, repo: str, pr_number: str) -> list: |
Collaborator
There was a problem hiding this comment.
Do we still want to keep these here in BugZooka or have it part of our new agentic workflow that we are looking at?
| 4. **Categorize by Severity** using absolute percentage change (ignore sign): | ||
| - **Significant**: |change| >= 10% | ||
| - **Moderate**: 5% <= |change| < 10% | ||
| - **Significant**: |change| >= 8% |
Collaborator
There was a problem hiding this comment.
Why are we changing from 10 to 8 here?
|
|
||
| BugZooka's PR analysis compares performance test results from a pull request against baseline metrics, classifies regressions and improvements, and — with the changes on this branch — autonomously investigates the PR's code changes to identify root causes. | ||
|
|
||
| **Before this branch:** The LLM receives performance metrics from Orion (via MCP tools) and can say "OVN CPU increased 15%" but has no visibility into the actual code changes, so it cannot explain *why* or recommend specific fixes. |
Collaborator
There was a problem hiding this comment.
Why do we want to make it sound like a Before/After changelog?
vishnuchalla
requested changes
Apr 24, 2026
Collaborator
vishnuchalla
left a comment
vishnuchalla
left a comment
There was a problem hiding this comment.
I like this idea but I think the tools here should be coded as our own custom version of GH MCP and be reused in here and in appropriate agentic workflows as well.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add 9 GitHub investigation tools (pr_tools.py) that let the LLM autonomously explore PR diffs, commits, file contents, and metadata during regression analysis. Integrate tools with MCP/Orion tools in pr_analyzer.py. Update prompts with funnel investigation strategy (scope assessment, adaptive small/large PR handling, subsystem mapping), lower severity thresholds to 8%, and add test file exclusion guardrails.
Includes developer documentation at docs/enhancement-pr-analysis.md.