pr-management-triagelisted

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Placeholder convention: <repo> → target GitHub repository in `owner/name` form (default: read from `<project-config>/project.md → upstream_repo`) <viewer> → the authenticated GitHub login of the maintainer running the skill <base> → the PR's base branch (typically `main`) Substitute these before running any `gh` command below. --> # pr-management-triage This skill walks a maintainer through **first-pass triage** of open pull requests. Its job is to answer, for each candidate PR, one question: > *What is the next move — draft, comment, close, rebase, rerun, > mark ready, ping, or leave alone?* It is the on-ramp of the PR lifecycle. Everything after this skill — detailed code review, line-level comments, approve / request-changes — belongs to a separate review skill and is out of scope here. This skill is the successor to the triage mode of `breeze pr auto-triage`. It drops the full-screen TUI in favour of a CLI conversation. The flow is: 1. **Fetch the entire candidate set up front** by paginating through GitHub until `has_next_page=false`. The fetch is a no-attention phase — the maintainer can step away while the skill walks the pages. 2. **Classify every fetched PR in one pass**, building groups that span the whole queue (a `mark-ready` group may carry 30 PRs across what was previously six pages). 3. **Present groups to the maintain