dotnet
Finds open PRs in the dotnet/maui and dotnet/docs-maui repositories that are good candidates for review, prioritizing by milestone, priority labels, partner/community status.
bunx add-skill dotnet/maui -s find-reviewable-prLoadingβ¦
This skill searches the dotnet/maui and dotnet/docs-maui repositories for open pull requests that are good candidates for review, prioritized by importance.
# Find all reviewable PRs (shows top from each category including docs-maui)
pwsh .github/skills/find-reviewable-pr/scripts/query-reviewable-prs.ps1
# Find only milestoned PRs
pwsh .github/skills/find-reviewable-pr/scripts/query-reviewable-prs.ps1 -Category milestoned
# Find only docs-maui PRs waiting for review
pwsh .github/skills/find-reviewable-pr/scripts/query-reviewable-prs.ps1 -Category docs-maui
# Find recent PRs waiting for review
pwsh .github/skills/find-reviewable-pr/scripts/query-reviewable-prs.ps1 -Category recent
# Find Android PRs only
pwsh .github/skills/find-reviewable-pr/scripts/query-reviewable-prs.ps1 -Platform android
# Limit results per category
pwsh .github/skills/find-reviewable-pr/scripts/query-reviewable-prs.ps1 -Limit 5
# Adjust docs-maui limit (default is 5, minimum enforced)
pwsh .github/skills/find-reviewable-pr/scripts/query-reviewable-prs.ps1 -DocsLimit 10
| Parameter | Values | Default | Description |
|---|---|---|---|
-Category | milestoned, priority, recent, partner, community, docs-maui, all | all | Filter by category |
-Platform | android, ios, windows, maccatalyst, all | all | Filter by platform |
-Limit | 1-100 | 10 | Max PRs per category (maui repo) |
-RecentLimit | 1-100 | 5 | Max recent PRs waiting for review from maui repo (minimum 5 enforced) |
-DocsLimit | 1-100 | 5 | Max PRs for docs-maui waiting for review (minimum 5 enforced) |
-ExcludeAuthors | string[] | (none) | Exclude PRs from specific authors (e.g., -ExcludeAuthors PureWeen,rmarinho) |
-IncludeAuthors | string[] | (none) | Only include PRs from specific authors |
-OutputFormat | review, table, json | review | Output format |
CRITICAL: You MUST use the PowerShell script below. Do NOT attempt to query GitHub directly with gh commands or jq if the script fails. The script contains important prioritization logic (SR3 before SR4, P/0 first, etc.) that cannot be replicated with ad-hoc queries.
pwsh .github/skills/find-reviewable-pr/scripts/query-reviewable-prs.ps1 -Limit 5
If the script fails (e.g., HTTP 502, network error, authentication issue):
Why no fallbacks? Ad-hoc queries bypass the milestone prioritization logic and will return incorrectly ordered results (e.g., later SR milestones before earlier ones).
IMPORTANT: If the script output contains a warning about missing read:project scope, you MUST include this warning at the TOP of your response to the user:
β οΈ **Note**: Your GitHub token is missing the `read:project` scope. Project board data is not available.
To enable: `gh auth refresh -s read:project`
CRITICAL: When presenting PR results, you MUST include PRs from ALL categories returned by the script:
DO NOT omit any category. Each category table should include columns for: PR, Title, Author, Platform/Repo, Status, Age, Updated.
When user asks to review, present only ONE PR in this format:
## PR #XXXXX
**[Title]**
π [URL]
| Field | Value |
|-------|-------|
| **Author** | username |
| **Platform** | platform |
| **Complexity** | Easy/Medium/Complex |
| **Milestone** | milestone or (none) |
| **Age** | X days |
| **Files** | X (+additions/-deletions) |
| **Labels** | labels |
| **Category** | priority/milestoned/partner/community/recent |
Would you like me to review this PR?
When user confirms, use the pr agent:
| Complexity | Criteria |
|---|---|
| Easy | β€5 files, β€200 additions |
| Medium | 6-15 files, or 200-500 additions |
| Complex | >15 files, or >500 additions |
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.