| Limit N (default 20) | "triage top 10 PRs" | `--limit N` |
| Area label | "triage area-System.Net PRs" | `--label area-System.Net` |
| Author | "triage PRs by stephentoub" | `--author stephentoub` |
| Exclude drafts (default on) | — | Filter `isDraft: false` |
| Exclude bots (default on) | — | Filter out `app/dotnet-maestro`, `app/copilot-swe-agent` |
| Exclude `needs-author-action` | "show PRs ready for maintainer" | Filter out label |
| Exclude `no-recent-activity` (default on) | — | Filter out label |
| Recently updated | "triage PRs updated this week" | `--sort updated` + date filter |
| Date range | "triage PRs opened in last 30 days" | Filter by `createdAt` or `updatedAt` |
| Community PRs | "triage community contributions" | `--label community-contribution` |
| Has maintainer approval | "show approved PRs" | Pass 2 filter: check reviews |
| Green Build Analysis | "show PRs with passing CI" | Pass 2 filter: check Build Analysis |
| Small/localized | "triage simple PRs" | Pass 2 filter: changedFiles, additions, deletions |

## Pass 1 — Quick-Screen

```bash
gh pr list --repo dotnet/runtime --state open --limit 100 \
  --json number,title,author,labels,isDraft,mergeable,createdAt,updatedAt,changedFiles,additions,deletions

**.github/skills/pr-triage/scripts/Get-PrTriageData.ps1:36**
* The help text says `-Limit` defaults to 100 (line 10), but the parameter default is 500 (line 36). This mismatch will confuse callers; update either the comment or the default value so they agree.

**.github/skills/pr-triage/scripts/Get-PrTriageData.ps1:57**
* Area owner parsing filters out any `@dotnet/<team>` mentions (`Where-Object { $_ -notmatch '^dotnet/' }`). In dotnet/runtime's `docs/area-owners.md`, many areas list owners as GitHub teams (e.g., `@dotnet/ncl`, `@dotnet/area-*`), so this will drop the primary owners and can make maintainer-approval detection and `who` tagging inaccurate. Consider retaining team handles for tagging and/or handling team-only rows explicitly (e.g., keep teams in the owner list instead of discarding them).

    if ($line -match '^\|\s*(area-\S+)\s*\|\s*@(\S+)\s*\|\s*(.+?)\s*\|') {
        $areaName = $matches[1].Trim()
        $lead = $matches[2].Trim()
        $ownerField = $matches[3].Trim()
        $people = @([regex]::Matches($ownerField, '@(\S+)') | ForEach-Object { $_.Groups[1].Value } |
            Where-Object { $_ -notmatch '^dotnet/' })
        if ($people.Count -eq 0) { $people = @($lead) }

**.github/skills/pr-triage/scripts/Get-PrTriageData.ps1:85**
* `$copilotAgent` is computed but never used, which is dead code and suggests an incomplete filter/reporting feature. Either remove it or use it (e.g., include in the scanned/excluded summary if intended).

**.github/skills/pr-triage/scripts/Get-PrTriageData.ps1:348**
* `next_action` selection checks `-not $hasAnyReview` before checking Build Analysis failure. That means a PR with red CI and no reviews will be classified as "Maintainer: review needed" even though CI is a hard blocker per the rubric. Consider prioritizing CI failure/pending ahead of review-needed so the suggested next step reflects merge blockers.

elseif (-not $hasAnyReview) {
    $prNextAction = "Maintainer: review needed"
    # Pick specific owners to tag: prefer owners who have reviewed similar PRs
    if ($prOwners.Count -gt 0) {
        $who = @($prOwners | Select-Object -First 2)
    } else {
        $who = @("area owner")
    }
}
elseif ($baConclusion -eq "FAILURE") {
    $prNextAction = "Author: fix CI failures"
    $who = @($pr.author.login)
}

**.github/skills/pr-triage/SKILL.md:305**
* This section says the script scores **11** dimensions, but the implementation includes an additional "Discussion complexity" dimension (`$discussionScore * 1.5`) in the composite. Update the documentation to match the actual dimensions/weights used so users can interpret scores correctly.

**.github/skills/pr-triage/references/runtime-signals.md:17**
* The label taxonomy says `community-contribution` should "Boost priority", but the scoring rubric (and the script) treat community PRs as lower-scoring / flagged rather than boosted. Reword this triage impact to match the rubric (e.g., "Flag for visibility / consider prioritizing") so the guidance is consistent.

**.github/skills/pr-triage/SKILL.md:24**
* The PR title/description are about adding the `pr-triage` skill, but this PR also changes the regex engine and adds a new regression test under `System.Text.RegularExpressions`. That looks like an unrelated product change and will make the PR harder to review/land; consider splitting the regex fix into a separate PR (or updating the PR description to explicitly cover it).

**.github/skills/pr-triage/scripts/Get-PrTriageData.ps1:288**
* `$feedbackScore` only considers unresolved review threads. If `-IncludeNeedsAuthor` is used, PRs with the `needs-author-action` label can be included but still score as fully addressing feedback when threads are resolved/absent, which contradicts the label meaning (blocking). Consider incorporating the label into feedback scoring (e.g., `needs-author-action` => 0.0) and/or into `next_action` selection.

# Labels
$isCommunity = $labelNames -contains "community-contribution"
$hasAreaLabel = ($labelNames | Where-Object { $_ -match "^area-" }).Count -gt 0
$isUntriaged = $labelNames -contains "untriaged"

# Dates
$updatedAt = [DateTime]::Parse($pr.updatedAt)
$createdAt = [DateTime]::Parse($pr.createdAt)
$daysSinceUpdate = ($now - $updatedAt).TotalDays
$ageInDays = ($now - $createdAt).TotalDays

# Check counts
$passed = @($checks | Where-Object { $_.conclusion -eq "SUCCESS" }).Count
$failed = @($checks | Where-Object { $_.conclusion -eq "FAILURE" }).Count
$running = @($checks | Where-Object { $_.status -eq "IN_PROGRESS" -or $_.status -eq "QUEUED" }).Count

# --- DIMENSION SCORING ---
$ciScore = switch ($baConclusion) { "SUCCESS" { 1.0 } "ABSENT" { 0.5 } "IN_PROGRESS" { 0.5 } default { 0.0 } }
$stalenessScore = if ($daysSinceUpdate -le 3) { 1.0 } elseif ($daysSinceUpdate -le 14) { 0.5 } else { 0.0 }
$maintScore = if ($hasOwnerApproval) { 1.0 } elseif ($hasTriagerApproval) { 0.75 } elseif ($hasAnyReview) { 0.5 } else { 0.0 }
$feedbackScore = if ($unresolvedThreads -eq 0) { 1.0 } else { 0.5 }
$conflictScore = switch ($pr.mergeable) { "MERGEABLE" { 1.0 } "UNKNOWN" { 0.5 } "CONFLICTING" { 0.0 } default { 0.5 } }

**.github/skills/pr-triage/scripts/Get-PrTriageData.ps1:314**
* `$alignScore` is capped at 0.5 when aligned, but the composite normalization assumes a max weight sum of 20.0 (which implies alignment can contribute 1.0). As written, no PR can reach the documented maximum score because alignment never hits 1.0. Either make aligned PRs score 1.0 (when they have an area label and are not untriaged) or adjust `$rawMax`/weights to match the implemented scoring.

$alignScore = if ($isUntriaged -or -not $hasAreaLabel) { 0.0 } else { 0.5 }
$freshScore = if ($daysSinceUpdate -le 14) { 1.0 } elseif ($daysSinceUpdate -le 30) { 0.5 } else { 0.0 }
$totalLines = $pr.additions + $pr.deletions
$sizeScore = if ($pr.changedFiles -le 5 -and $totalLines -le 200) { 1.0 } elseif ($pr.changedFiles -le 20 -and $totalLines -le 500) { 0.5 } else { 0.0 }
$communityScore = if ($isCommunity) { 0.5 } else { 1.0 }
$approvalScore = if ($approvalCount -ge 2 -and $hasOwnerApproval) { 1.0 }
                 elseif ($hasOwnerApproval -or ($hasTriagerApproval -and $approvalCount -ge 2)) { 0.75 }
                 elseif ($hasTriagerApproval -or $approvalCount -ge 2) { 0.5 }
                 elseif ($approvalCount -ge 1) { 0.5 }
                 else { 0.0 }
$velocityScore = if ($reviews.Count -eq 0) { if ($ageInDays -le 14) { 0.5 } else { 0.0 } }
                 elseif ($daysSinceUpdate -le 7) { 1.0 } elseif ($daysSinceUpdate -le 14) { 0.5 } else { 0.0 }
# Discussion complexity: many threads/commenters = harder to push forward
# Light (≤5 threads, ≤2 commenters) = 1.0, moderate = 0.5, heavy (>15 threads or >5 commenters) = 0.0
$discussionScore = if ($totalThreads -le 5 -and $distinctCommenters -le 2) { 1.0 }
                   elseif ($totalThreads -le 15 -and $distinctCommenters -le 5) { 0.5 }
                   else { 0.0 }

# Composite: weighted sum normalized to 0-10 scale
$rawMax = 20.0
$rawScore = ($ciScore * 3) + ($conflictScore * 3) + ($maintScore * 3) +
    ($feedbackScore * 2) + ($approvalScore * 2) + ($stalenessScore * 1.5) +
    ($discussionScore * 1.5) +
    ($alignScore * 1) + ($freshScore * 1) + ($sizeScore * 1) +
    ($communityScore * 0.5) + ($velocityScore * 0.5)
$composite = [Math]::Round(($rawScore / $rawMax) * 10, 1)

**.github/skills/pr-triage/scripts/Get-PrTriageData.ps1:521**
* The `-OutputCsv` path writes tab-separated data that includes untrusted PR metadata such as `title`, `who`, `next_action`, `blockers`, and `why` directly into cells without sanitization. If a PR title or other field begins with spreadsheet metacharacters (e.g., `=`, `+`, `-`, `@`), opening this TSV in Excel or similar tools can trigger formula execution (CSV/TSV injection), allowing data exfiltration or command execution via spreadsheet functions. To mitigate this, sanitize or escape these fields before emitting them for spreadsheet import (for example, by prefixing values that start with these characters with a safe character or otherwise neutralizing formula evaluation).

foreach ($r in $results) {
    $t = ($r.title -replace "`t"," ").Substring(0, [Math]::Min(70, $r.title.Length))
    $lines += "$($r.number)`t$t`t$($r.author)`t$($r.score)`t$($r.ci)`t$($r.ci_detail)`t$($r.unresolved_threads)`t$($r.total_threads)`t$($r.distinct_commenters)`t$($r.mergeable)`t$($r.approval_count)`t$(if ($r.is_community) {1} else {0})`t$($r.age_days)`t$($r.days_since_update)`t$($r.changed_files)`t$($r.lines_changed)`t$($r.next_action)`t$($r.who)`t$($r.blockers)`t$($r.why)"

</details>

**Fallback**: If the PR has no area label, use `.github/CODEOWNERS` to match file paths to reviewers.

    elseif ($daysSinceUpdate -gt 14) {
        $prNextAction = "Author: merge main (stale $([int]$daysSinceUpdate)d)"
        $who = @($pr.author.login)
    }
    elseif ($ciScore -eq 1 -and $conflictScore -eq 1 -and $maintScore -ge 0.75 -and $feedbackScore -eq 1) {

$communityTriagers = @("a74nh","am11","clamp03","Clockwork-Muse","filipnavara",
    "huoyaoyuan","martincostello","omajid","Sergio0694","shushanhf",
    "SingleAccretion","teo-tsirpanis","tmds","vcsjones","xoofx")

$fragment = 'number comments{totalCount} reviews(last:10){nodes{author{login}state}} reviewThreads(first:50){nodes{isResolved comments(first:5){nodes{author{login}}}}} commits(last:1){nodes{commit{statusCheckRollup{contexts(first:100){nodes{...on CheckRun{name conclusion status}}}}}}}'

    $threadCommentSum = if ($gql -and $gql.reviewThreads.nodes) {
        ($gql.reviewThreads.nodes | ForEach-Object { $_.comments.nodes.Count } | Measure-Object -Sum).Sum
    } else { 0 }

| **1. Area owner/lead** | Listed in Owners/Lead column of `docs/area-owners.md` for the PR's area label | Parse area-owners.md, match reviewer login against Owners column | Has merge authority for the area |
| **2. Community triager** | Trusted community members with triage permissions, listed in area-owners.md | Parse the "Community Triagers" section at the bottom of `docs/area-owners.md` | Strong signal — deeply familiar with the repo. Does not have merge authority but review is highly valued. |
| **3. Frequent contributor** | Has many merged PRs or commits in the touched area | `gh api "repos/dotnet/runtime/commits?author={login}&path={dir}&per_page=5"` — 3+ hits = frequent | Valuable domain expertise. Weight 1× (standard). |
| **4. New contributor** | First-time or infrequent contributor to this area | No commits found in touched paths | Review appreciated — every contributor's feedback helps improve the PR. Weight 0.5×. |

if ($OutputCsv) {
    # Tab-separated output for easy SQL/spreadsheet import
    $header = "number`ttitle`tauthor`tscore`tci`tci_detail`tunresolved_threads`ttotal_threads`ttotal_comments`tdistinct_commenters`tmergeable`tapproval_count`tis_community`tage_days`tdays_since_update`tchanged_files`tlines_changed`tnext_action`twho`tblockers`twhy"

## Search Helix Logs and Artifacts Remotely

> 💡 **Prefer remote search over download.** `hlx_search_log` and `hlx_search_file` let you find errors in Helix console logs and uploaded files without downloading them first. Use these before falling back to `hlx_logs` (full log) or `hlx_download` (file download).

        $t = ($r.title -replace "`t"," ").Substring(0, [Math]::Min(70, $r.title.Length))
        $lines += "$($r.number)`t$t`t$($r.author)`t$($r.score)`t$($r.ci)`t$($r.ci_detail)`t$($r.unresolved_threads)`t$($r.total_threads)`t$($r.total_comments)`t$($r.distinct_commenters)`t$($r.mergeable)`t$($r.approval_count)`t$(if ($r.is_community) {1} else {0})`t$($r.age_days)`t$($r.days_since_update)`t$($r.changed_files)`t$($r.lines_changed)`t$($r.next_action)`t$($r.who)`t$($r.blockers)`t$($r.why)"

# --- Step 3: Batched GraphQL (reviews, threads, Build Analysis, thread authors) ---
$fragment = 'number comments{totalCount} reviews(last:10){nodes{author{login}state}} reviewThreads(first:50){nodes{isResolved comments(first:5){nodes{author{login}}}}} commits(last:1){nodes{commit{statusCheckRollup{contexts(first:100){nodes{...on CheckRun{name conclusion status}}}}}}}'

        drafts_count = $drafts.Count
        drafts = @($drafts | Select-Object -First 10 | ForEach-Object { @{ number = $_.number; author = $_.author.login; title = $_.title.Substring(0, [Math]::Min(60, $_.title.Length)) } })
        bots = @($bots | ForEach-Object { @{ number = $_.number; author = $_.author.login } })
        needs_author_action = @($needsAuthor | ForEach-Object { @{ number = $_.number; author = $_.author.login } })
        stale = @($stale | ForEach-Object { @{ number = $_.number; author = $_.author.login } })

**Note**: The script parses `docs/area-owners.md` dynamically at startup to get
the full owner table (~138 areas). Do not rely on hardcoded owner lists.

# --- Step 3: Batched GraphQL (reviews, threads, Build Analysis, thread authors) ---
$fragment = 'number comments{totalCount} reviews(last:10){nodes{author{login}state}} reviewThreads(first:50){nodes{isResolved comments(first:5){nodes{author{login}}}}} commits(last:1){nodes{commit{statusCheckRollup{contexts(first:100){nodes{...on CheckRun{name conclusion status}}}}}}}'

**Fallback**: If the PR has no area label, use `.github/CODEOWNERS` to match file paths to reviewers.

**Max possible raw score**: 20.5. Normalized to a 0–10 scale: `(rawScore / 20.5) × 10`.

    $repoOwner = $repoParts[0]
    $repoName = $repoParts[1]
    $query = "{ repository(owner:`"$repoOwner`",name:`"$repoName`") { $($parts -join ' ') } }"
    $result = gh api graphql -f query="$query" 2>&1 | ConvertFrom-Json
    for ($i = 0; $i -lt $b.Count; $i++) {

        if ($line -match '^\|\s*(area-\S+)\s*\|\s*@(\S+)\s*\|\s*(.+?)\s*\|') {
            $areaName = $matches[1].Trim()
            $lead = $matches[2].Trim()
            $ownerField = $matches[3].Trim()
            $people = @([regex]::Matches($ownerField, '@(\S+)') | ForEach-Object { $_.Groups[1].Value } |
                Where-Object { $_ -notmatch '^dotnet/' })
            if ($people.Count -eq 0) { $people = @($lead) }
            $areaOwners[$areaName] = $people

    # Composite: weighted sum normalized to 0-10 scale
    $rawMax = 20.5
    $rawScore = ($ciScore * 3) + ($conflictScore * 3) + ($maintScore * 3) +
        ($feedbackScore * 2) + ($approvalScore * 2) + ($stalenessScore * 1.5) +
        ($discussionScore * 1.5) +
        ($alignScore * 1) + ($freshScore * 1) + ($sizeScore * 1) +
        ($communityScore * 0.5) + ($velocityScore * 0.5)

    # --- DIMENSION SCORING ---
    $ciScore = switch ($baConclusion) { "SUCCESS" { 1.0 } "ABSENT" { 0.5 } "IN_PROGRESS" { 0.5 } default { 0.0 } }
    $stalenessScore = if ($daysSinceUpdate -le 3) { 1.0 } elseif ($daysSinceUpdate -le 14) { 0.5 } else { 0.0 }
    $maintScore = if ($hasOwnerApproval) { 1.0 } elseif ($hasTriagerApproval) { 0.75 } elseif ($hasAnyReview) { 0.5 } else { 0.0 }
    $hasNeedsAuthorAction = $labelNames -contains "needs-author-action"
    $feedbackScore = if ($hasNeedsAuthorAction) { 0.0 } elseif ($unresolvedThreads -eq 0) { 1.0 } else { 0.5 }
    $conflictScore = switch ($pr.mergeable) { "MERGEABLE" { 1.0 } "UNKNOWN" { 0.5 } "CONFLICTING" { 0.0 } default { 0.5 } }
    $alignScore = if ($isUntriaged -or -not $hasAreaLabel) { 0.0 } else { 1.0 }
    $freshScore = if ($daysSinceUpdate -le 14) { 1.0 } elseif ($daysSinceUpdate -le 30) { 0.5 } else { 0.0 }
    $totalLines = $pr.additions + $pr.deletions

$communityTriagers = @("a74nh","am11","clamp03","Clockwork-Muse","filipnavara",
    "huoyaoyuan","martincostello","omajid","Sergio0694","shushanhf",
    "SingleAccretion","teo-tsirpanis","tmds","vcsjones","xoofx")

$areaOwners = @{}
$repoParts = $Repo -split '/'
$areaOwnersUrl = "repos/$($repoParts[0])/$($repoParts[1])/contents/docs/area-owners.md"

        blocked_conflicts = @($results | Where-Object { $_.mergeable -eq "CONFLICTING" }).Count
    }
    prs = @($results)
    elapsed_seconds = [Math]::Round(((Get-Date) - $scriptStart).TotalSeconds, 1)
}

if ($OutputCsv) {

$excludedDrafts = if ($IncludeDrafts) { 0 } else { $drafts.Count }
$excludedBots = $bots.Count
Write-Verbose "Scanned $($prsRaw.Count) -> $($candidates.Count) candidates ($excludedDrafts drafts, $excludedBots bots, $($needsAuthor.Count) needs-author, $($stale.Count) stale excluded)"

    foreach ($r in $results) {
        $t = ($r.title -replace "`t"," ").Substring(0, [Math]::Min(70, $r.title.Length))
        if ($t.Length -gt 0 -and $t[0] -in '=','+','-','@') { $t = "'$t" }
        $lines += "$($r.number)`t$t`t$($r.author)`t$($r.score)`t$($r.ci)`t$($r.ci_detail)`t$($r.unresolved_threads)`t$($r.total_threads)`t$($r.total_comments)`t$($r.distinct_commenters)`t$($r.mergeable)`t$($r.approval_count)`t$(if ($r.is_community) {1} else {0})`t$($r.age_days)`t$($r.days_since_update)`t$($r.changed_files)`t$($r.lines_changed)`t$($r.next_action)`t$($r.who)`t$($r.blockers)`t$($r.why)"

| # | Dimension | Weight | Rationale |
|---|-----------|--------|-----------|
| 1 | CI Status | 3 | Can't merge without green CI |
| 5 | Merge Conflicts | 3 | Can't merge with conflicts |
| 3 | Maintainer Review | 3 | Required for merge |
| 4 | Feedback Addressed | 2 | Blocks merge if outstanding |
| 12 | Approval Strength | 2 | Stronger approvals = closer to merge |
| 2 | Staleness | 1.5 | Days since last update |
| — | Discussion Complexity | 1.5 | Thread count and distinct commenters |
| 6 | Alignment | 1 | Organizational signal |
| 7 | Freshness | 1 | Stale PRs less likely to merge soon |
| 9 | PR Size / Complexity | 1 | Ease of review |
| 10 | Community Contribution Flag | 0.5 | Flags community PRs — typically more expensive to drive |
| 13 | Review Velocity | 0.5 | Momentum signal |

**Max possible raw score**: 20.5. Normalized to a 0–10 scale: `(rawScore / 20.5) × 10`.

### 2. Build Staleness

**How to check**

Compare `headRefOid` from `gh pr view` against build info from `gh pr checks`
timestamps.

**Scoring**

| Score | Condition |
|-------|-----------|
| ✅ 1 | Build ran on current HEAD and within last 3 days |
| ⚠️ 0.5 | Build is 3–14 days old |
| ❌ 0 | Build is >14 days old or ran on a different SHA than current HEAD |

**Next-action guidance**: Do NOT recommend "merge main / rebase" solely because
a build is a few days old. Running CI takes 2–3 hours, so a rebase is costly.
Only recommend rebase when:
- Build is >14 days old, OR
- Context drift (dimension 8) shows significant changes to touched directories, OR
- Build ran on a different SHA than current HEAD

A 7-day-old green build with no context drift is fine — the next action should
be whatever the other blocking dimensions indicate.

**Note**: The script parses `docs/area-owners.md` dynamically at startup to get
the full owner table (~138 areas). Do not rely on hardcoded owner lists.

**Fallback**: If the PR has no area label, use `.github/CODEOWNERS` to match file paths to reviewers.

---

## Approval Authority Levels

Not all approvals carry equal weight for merge decisions. This reflects dotnet/runtime's
governance model where area owners have merge authority — it is not a judgment of review quality.

| Level | Who | How to detect | Merge weight |
|-------|-----|--------------|--------------|
| **1. Area owner/lead** | Listed in Owners/Lead column of `docs/area-owners.md` for the PR's area label | Parse area-owners.md, match reviewer login against Owners column | Has merge authority for the area |
| **2. Community triager** | Trusted community members with triage permissions, listed in area-owners.md | Parse the "Community Triagers" section at the bottom of `docs/area-owners.md` | Strong signal — deeply familiar with the repo. Does not have merge authority but review is highly valued. |
| **3. Frequent contributor** | Has many merged PRs or commits in the touched area | `gh api "repos/dotnet/runtime/commits?author={login}&path={dir}&per_page=5"` — 3+ hits = frequent | Valuable domain expertise. Weight 1× (standard). |
| **4. New contributor** | First-time or infrequent contributor to this area | No commits found in touched paths | Review appreciated — every contributor's feedback helps improve the PR. Weight 0.5×. |

### Known Community Triagers

These are listed in the "Community Triagers" section of `docs/area-owners.md` and have triage permissions:

@a74nh, @am11, @clamp03, @Clockwork-Muse, @filipnavara, @huoyaoyuan, @martincostello, @omajid, @Sergio0694, @shushanhf, @SingleAccretion, @teo-tsirpanis, @tmds, @vcsjones, @xoofx

A Community Triager's APPROVED review is a stronger signal than a new contributor's approval. They are deeply familiar with the repo, its conventions, and its quality bar — but they are not area owners and their approval alone does not satisfy the "maintainer review" dimension.

$repoParts = $Repo -split '/'
$areaOwnersUrl = "repos/$($repoParts[0])/$($repoParts[1])/contents/docs/area-owners.md"

$communityTriagers = @("a74nh","am11","clamp03","Clockwork-Muse","filipnavara",
    "huoyaoyuan","martincostello","omajid","Sergio0694","shushanhf",
    "SingleAccretion","teo-tsirpanis","tmds","vcsjones","xoofx")

**Max possible raw score**: 20.5. Normalized to a 0–10 scale: `(rawScore / 20.5) × 10`.

| **1. Area owner/lead** | Listed in Owners/Lead column of `docs/area-owners.md` for the PR's area label | Parse area-owners.md, match reviewer login against Owners column | Has merge authority for the area |
| **2. Community triager** | Trusted community members with triage permissions, listed in area-owners.md | Parse the "Community Triagers" section at the bottom of `docs/area-owners.md` | Strong signal — deeply familiar with the repo. Does not have merge authority but review is highly valued. |
| **3. Frequent contributor** | Has many merged PRs or commits in the touched area | `gh api "repos/dotnet/runtime/commits?author={login}&path={dir}&per_page=5"` — 3+ hits = frequent | Valuable domain expertise. Weight 1× (standard). |

    [string]$NextAction,
    [string]$PrNumber,
    [int]$Top = 0,

} catch {
    Write-Verbose "Warning: could not fetch area-owners.md, using empty owner table"
}

if ($OutputCsv) {
    # Tab-separated output for easy SQL/spreadsheet import
    $header = "number`ttitle`tauthor`tscore`tci`tci_detail`tunresolved_threads`ttotal_threads`ttotal_comments`tdistinct_commenters`tmergeable`tapproval_count`tis_community`tage_days`tdays_since_update`tchanged_files`tlines_changed`tnext_action`twho`tblockers`twhy"

**Note**: The script parses `docs/area-owners.md` dynamically at startup to get
the full owner table (~138 areas). Do not rely on hardcoded owner lists.

**Fallback**: If the PR has no area label, use `.github/CODEOWNERS` to match file paths to reviewers.

**Fallback**: If the PR has no area label, use `.github/CODEOWNERS` to match file paths to reviewers.

**Max possible raw score**: 20.5. Normalized to a 0–10 scale: `(rawScore / 20.5) × 10`.

| Score | PR | Title | Who | Next Action | CI | Disc | Age | Updated | Files | Author |
|------:|---:|-------|-----|-------------|----|-----:|----:|--------:|------:|--------|
| 8.4 | [#123546](https://github.com/dotnet/runtime/pull/123546) | arm64: Remove widening casts before truncating | @EgorBo | Ready to merge ✅ | ✅ 91/2/0 | 1t/2p | 5d | 1d | 3 | @jonathandavies-arm |
| 7.9 | [#122485](https://github.com/dotnet/runtime/pull/122485) | [RISC-V] Enable instruction printing | @SkyShield | Author: merge main (stale 17d) | ✅ 91/2/0 | 1t/2p | 24d | 17d | 2 | @SkyShield |
| ... | | | | | | | | | | |

$communityTriagers = @("a74nh","am11","clamp03","Clockwork-Muse","filipnavara",
    "huoyaoyuan","martincostello","omajid","Sergio0694","shushanhf",
    "SingleAccretion","teo-tsirpanis","tmds","vcsjones","xoofx")

    foreach ($rev in $reviews) {
        $login = $rev.author.login
        $reviewerLogins += $login
        if ($rev.state -eq "APPROVED") {
            $approvalCount++
            $hasAnyApproval = $true
            $approverLogins += $login
            # Check if approval is on the current head commit
            $isStale = $headCommitOid -and $rev.commit -and $rev.commit.oid -and ($rev.commit.oid -ne $headCommitOid)
            if ($isStale) { $hasStaleApproval = $true }
            if ($prOwners -contains $login) { $hasOwnerApproval = $true }
            elseif ($communityTriagers -contains $login) { $hasTriagerApproval = $true }
        }
    }