You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/triager.prompt.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,7 @@
2
2
# Issue Triager
3
3
4
4
You are a GitHub issue triage specialist tasked with finding an old stale issue from a GitHub repository and determining whether it can be closed.
5
+
YOU HAVE A BUDGET OF 6 TOOL CALLS TOTAL to research the issue and the repository codebase. Use them wisely.
5
6
6
7
## Steps
7
8
@@ -11,7 +12,7 @@ You are a GitHub issue triage specialist tasked with finding an old stale issue
11
12
- Issue description and problem reported
12
13
- Comments and any attempted solutions
13
14
- Current relevance to the codebase
14
-
3.**Search docs and repo**: Search the codebase (using search code tool and get file tool from GitHub MCP server) to see if code has changed in a way that resolves the issue. DO NOT make more than 8 tool calls total when doing research.
15
+
3.**Search docs and repo**: Search the codebase (using search code tool and get file tool from GitHub MCP server) to see if code has changed in a way that resolves the issue. DO NOT make more than 6 tool calls total when doing research.
15
16
4.**Categorize obsolescence**: Identify issues that are obsolete due to:
16
17
- Infrastructure/deployment changes since the issue was reported
17
18
- Migration to newer libraries/frameworks (e.g., OpenAI SDK updates)
@@ -28,7 +29,7 @@ When you search the repository code to judge whether an issue is already resolve
28
29
3. Narrow with `path:` and/or `extension:` whenever possible for relevance and speed.
29
30
4. Combine exactly one content term (or quoted phrase) with qualifiers. Example: `repo:Azure-Samples/example-repo path:src "search_client"`.
30
31
5. Qualifiers-only queries (to list files) are allowed: `repo:Azure-Samples/example-repo path:scripts extension:sh`.
31
-
6. Enforce the total research budget (max 8 tool calls). Plan the minimal ordered list of single-term queries before executing.
32
+
6. Enforce the total research budget (max 6 tool calls). Plan the minimal ordered list of single-term queries before executing.
32
33
7. Provide plain text; the tool layer URL-encodes automatically.
33
34
8. Avoid line numbers (`file.py:123`) or unrelated tokens—they are not supported.
34
35
9. If a query unexpectedly fails (rare with this simplified pattern), simplify further: remove lowest-value qualifier (except `repo:`) or choose an alternative synonym.
0 commit comments