---
name: github-issue-triage
description: Triage open GitHub issues by type, priority and duplicate status. Use when the user asks to sort, label, prioritise or clean up a repository's issue backlog, or to find duplicates.
---

# Triage GitHub issues

Work from the issue list, read only the threads that matter, and propose changes. Change nothing on GitHub until the user confirms each label, comment or close.

## Steps

1. Get the repository and the filter the user wants, such as open issues, a label, or a date range. If the user gave none, start with open issues with no label.
2. List the issues with `list_issues`. Work in pages and say how many you covered.
3. For each issue worth a decision, read it with `issue_read` (methods `get` and `get_comments`). Skip threads that are plainly clear from the title.
4. Look for duplicates by searching the repository with `search_code` for the error text, function or feature the issue names. Record the likely original and how sure you are.
5. Group the issues: bug with reproduction steps, bug missing information, feature request, question, duplicate, stale.

## What to report

- A table of issues with number, group, proposed priority and the reason in one line.
- Duplicates with the issue each one probably duplicates.
- Missing information to request, with the exact question to ask the reporter.
- The label and comment changes you propose, waiting for the user's confirmation.

Do not close an issue on your own judgement. Propose closing it and let the user decide.