Skip to content

Commit 1a2352c

Browse files
lbarcziovanforro
andcommitted
Apply suggestions from code review
Co-authored-by: Nikola Forró <[email protected]>
1 parent 06d6b77 commit 1a2352c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

beeai/agents/triage_agent.py

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ def prompt(self) -> str:
111111
You are an agent tasked to analyze Jira issues for RHEL and identify the most efficient path to resolution,
112112
whether through a version rebase, a patch backport, or by requesting clarification when blocked.
113113
114-
**Important**: This agent focuses on bugs, CVEs, and technical defects that need code fixes.
114+
**Important**: Focus on bugs, CVEs, and technical defects that need code fixes.
115115
QE tasks, feature requests, refactoring, documentation, and other non-bug issues should be marked as "no-action".
116116
117117
Goal: Analyze the given issue to determine the correct course of action.
@@ -166,12 +166,12 @@ def prompt(self) -> str:
166166
2.2. Systematic Source Investigation
167167
* Identify the official upstream project from two sources:
168168
* Links from the Jira issue (if any direct upstream links are provided)
169-
* Package specfile (<package>.spec) in the GitLab repository: check the URL field or Source0 field for upstream project location
169+
* Package spec file (<package>.spec) in the GitLab repository: check the URL field or Source0 field for upstream project location
170170
171171
* Even if the Jira issue provides a direct link to a fix, you need to validate it
172172
* When no direct link is provided, you must proactively search for fixes - do not give up easily
173173
* Using the details from your analysis, search these sources:
174-
- Bug Trackers (for fixed bugs matching the issue title and description)
174+
- Bug Trackers (for fixed bugs matching the issue summary and description)
175175
- Git / Version Control (for commit messages, using keywords, CVE IDs, function names, etc.)
176176
* Be thorough in your search - try multiple search terms and approaches based on the issue details
177177
* Advanced investigation techniques:

0 commit comments

Comments
 (0)