review-alerts

Review Alerts

Show a prioritized summary of PRs waiting for the caller's review. Never starts an actual review.

Prerequisites

This skill expects:

• gh CLI installed and authenticated
• jq available on PATH

Step 1: Validate Inputs

This skill requires two parameters: repo (GitHub owner/name) and user (GitHub login).

If either is missing, ask the user:

I need two things to check your reviews:
- **repo**: GitHub repository (e.g., `owner/repo`)
- **user**: Your GitHub username (e.g., `octocat`)

Which repo and user should I check?

And stop until the user provides them. Do NOT auto-detect from git context or gh api user.

Step 2: Discover PRs

Run the bundled discovery script with explicit flags:

PR_JSON=$("<skill-dir>/find-my-reviews.sh" --detailed --repo "$REPO" --user "$USER")

Where <skill-dir> is the directory containing this SKILL.md file.

If the script returns an empty array ([]), respond with:

Nothing to review right now. Enjoy your day!

And stop.

Step 3: Assess Priority and Review Complexity

Priority

For each PR in the JSON, assign a priority level:

High (any of):

• Label contains: urgent, hotfix, blocking, critical, P0, P1, high-priority, expedite
• Base branch matches: release/*, hotfix/*, production
• Age 7+ days

Medium (any of):

• Age 3-7 days
• Moderate size with activity

Low:

• Created less than 3 days ago, no urgency signals

Sort: High first, then Medium, then Low. Within same priority, oldest first.

Review Complexity

For each PR, assess review complexity:

Low: changed_files <= 3 AND (additions + deletions) < 50 AND no security-sensitive paths High: changed_files > 15 OR (additions + deletions) > 500 OR touches auth/crypto/security paths Medium: everything else

Security-sensitive path patterns: auth/, crypto/, keychain/, Token, Password, Secret, security/, credential

Step 4: Format the Report as ASCII Table