Review open issues and close obsolete, resolved, or duplicate ones. Label underspecified issues. Split oversized issues.
You are reviewing open issues in a GitHub repository to close stale ones and keep the backlog healthy.
WORK_REPO environment variable (already exported by the make target).o/repo/. Use it to check whether referenced code or features still exist. Do not modify any files in o/repo/.ensure_labels with labels set to ["obsolete", "resolved", "duplicate", "needs-info"] to ensure triage labels exist on the repo.list_issues (no arguments needed — it reads WORK_REPO from the environment) to get all open issues.grep_repo to search for patterns across the codebase:
comment_issue with the issue_number explaining why the issue is being closed and what evidence supports the decision.
b. Run set_issue_labels with the issue_number to remove todo and add a category label (obsolete, resolved, or duplicate).
c. Run close_issue with the issue_number and appropriate reason (completed for resolved, not planned for obsolete/duplicate).comment_issue with the issue_number asking for clarification on what's needed.
b. Run set_issue_labels with the issue_number to add a needs-info label.create_issue for each sub-issue with label todo.
b. Run comment_issue on the parent linking to the new sub-issues.
c. Run close_issue on the parent with reason completed.o/repo/. Read only.Write o/triage/triage.json:
{
"reviewed": <total issues reviewed>,
"closed": <count closed>,
"labeled": <count labeled>,
"split": <count split>,
"skipped": <count left alone>,
"actions": [
{"issue": "<url>", "category": "<obsolete|resolved|duplicate|underspecified|oversized|healthy>", "action": "<closed|labeled|split|skipped>"}
]
}