GitHub
triage_issue
Triage an issue by capturing a focused triage rationale and optionally applying metadata (labels, issue type, and issue fields) in a single operation. Use this tool when: - You are triaging a newly opened or untriaged issue for maintainers - You need to categorize the issue (type) and suggest/apply relevant labels - You want to record a brief, structured triage report Do not use this tool when: - The user is asking a general product question unrelated to triaging a specific issue triage_rationale should be concise markdown aimed at maintainers (not the issue author); it should contain: - Summary of the issue - Analysis of the problem or request - Suggested next steps or actions.
Other tools also called triage_issue?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"repo": {
"type": "string",
"description": "Repository name"
},
"type": {
"type": "string",
"description": "The issue type to set (optional, e.g., 'bug', 'feature_request')"
},
"owner": {
"type": "string",
"description": "Repository owner (username or organization)"
},
"fields": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"value"
],
"properties": {
"name": {
"type": "string",
"description": "Field name"
},
"value": {
"description": "Field value (string, number, or other supported type)"
}
}
},
"description": "Custom fields to set on the issue (optional)"
},
"labels": {
"type": "array",
"items": {
"type": "string"
},
"description": "Labels to apply to the issue (optional)"
},
"issue_number": {
"type": "number",
"minimum": 1,
"description": "The issue number to triage"
},
"triage_rationale": {
"type": "string",
"description": "The triage comment body containing analysis and rationale. This will be posted as a comment on the issue."
}
}
}