pr-triage

Pull request triage identifies priority, overlapping, stale, and review-ready PRs within a backlog. It audits open pull requests by separating internal from external contributions, tracking CI status, draft state, and staleness to guide which code reviews require immediate action.

Prioritizing overlapping code reviews requires auditing open PRs to detect intersections and staleness. Triage generates a table separating internal vs external PRs, tracking CI status and reviewer readiness, ensuring developers address the most critical code changes first.

Git worktrees can be set up for local testing during the optional fourth phase of the PR triage workflow. After auditing priorities and deep reviewing code, worktrees are configured to allow local validation before any comments are posted or changes are applied.

PR triage does not post comments automatically; it requires explicit user validation before any posting or changes occur. Draft comments are generated during the workflow, but safe operation is enforced by ensuring a user confirms all actions beforehand.

The best way to review a large backlog is a multi-phase workflow: audit open PRs for priorities, perform optional deep reviews via parallel agents, draft validated comments, and optionally set up worktrees. This surfaces staleness, overlaps, and CI status to guide action.

Deep review works as the optional second phase of PR triage, utilizing parallel agents to analyze code changes after the initial audit. It follows the audit phase and precedes drafting comments, allowing thorough examination of complex pull requests before action.