pr-dashboard

name	pr-dashboard
description	Review open PRs authored by the user for a given repo, showing title, status, review state, open comments, CI checks, and recommended next steps. Use when the user mentions PR review, my PRs, open PRs, PR status, PR dashboard, or wants an overview of their pull requests.

PR Review Dashboard

Generate a status overview of the user's open PRs for a given repository.

Resolve the Repository

The user provides a shorthand name (e.g., "my-app", "api-server"). Resolve it to owner/repo:

1. Run: gh repo list --json nameWithOwner --limit 200 -q '.[].nameWithOwner' and filter for a repo name containing the shorthand.
2. If multiple matches, pick the closest match or ask the user.
3. If the user provides owner/repo directly, use it as-is.

Fetch PR Data

gh pr list --repo OWNER/REPO --author @me --state open \
  --json number,title,url,isDraft,reviewDecision,updatedAt,additions,deletions,labels,headRefName

If no PRs are found, report that and stop.

For each PR, fetch detailed review and check info:

gh pr view NUMBER --repo OWNER/REPO \
  --json reviewDecision,reviews,comments,statusCheckRollup,mergeable,mergeStateStatus

Status Icon

Assign each PR a single status icon. This icon is used both in the detail rows and in the copy-paste summary. Pick the first matching rule, in priority order:

Icon	Meaning	Condition
🔴	CI failing	statusCheckRollup has any failing check
🟠	Changes requested	reviewDecision = CHANGES_REQUESTED
📝	Draft	isDraft = true
🟡	Awaiting review	review pending / no reviewers / CI still pending
🟢	Green — ready to merge	reviewDecision = APPROVED and all CI checks passing

Build the Report

For each PR, present a row with:

Field	Source
Title	title
PR	#number as a markdown link to url
Branch	headRefName
Size	+additions / -deletions
Draft?	isDraft → "Draft" or "Ready"
Reviews	Summarize from reviewDecision: APPROVED → "Approved", CHANGES_REQUESTED → "Changes requested", REVIEW_REQUIRED → "Awaiting review", empty → "No reviewers"
CI	From statusCheckRollup: count pass/fail/pending. Show "All passing", "N failing", or "Pending"
Comments	Count of unresolved review comments from comments and reviews
Updated	Relative time from updatedAt

Recommended Next Step

Derive one recommended action per PR using this priority:

1. CI failing → "Fix failing checks"
2. Changes requested → "Address review feedback"
3. Draft → "Mark as ready for review when done"
4. No reviewers → "Request reviewers"
5. Awaiting review → "Waiting on reviewers — consider pinging if stale (>3 days)"
6. Approved + CI passing → "Ready to merge"
7. Approved + CI pending → "Wait for CI, then merge"

Output Format

## PR Dashboard: {owner/repo}

### {icon} 1. {title}
- **PR**: [#{number}]({url}) | **Branch**: `{branch}`
- **Size**: +{additions} / -{deletions} | **Updated**: {relative_time}
- **Status**: {Draft/Ready} | **Reviews**: {review_summary} | **CI**: {ci_summary}
- **Open comments**: {count}
- **→ Next step**: {recommendation}

---
(repeat for each PR)

Copy-Paste Summary

After the detailed report, always end with a copy-paste summary block. This is the part the user drops straight into a Slack message — keep it tight: one line per PR, just the status icon followed by the PR title as a link to its GitHub URL. No branch, size, or extra metadata.

**PR dashboard check — {owner/repo}**

{icon} [{title}]({url})
{icon} [{title}]({url})
{icon} [{title}]({url})

Notes:

• Use the markdown link [{title}]({url}) so the title is clickable and lands on the PR in GitHub.
• One PR per line, nothing else — this keeps it clean to paste into Slack.
• Sort the lines by priority so the most urgent PRs are on top: 🔴 failing → 🟠 changes requested → 📝 draft → 🟡 awaiting review → 🟢 ready to merge.

Sort the detailed report by the same priority order.