// Bulk review all unreviewed pull requests for the awesome-quant curated list. Review all open PRs without the "reviewed" label in one session, then present a summary table for user selection before merging. Use this skill when asked to "bulk review", "review all prs", "bprr", or "review unreviewed".
[HINT] تحميل مجلد المهارة الكامل بما في ذلك SKILL.md وجميع الملفات المرتبطة
| name | bprr |
| description | Bulk review all unreviewed pull requests for the awesome-quant curated list. Review all open PRs without the "reviewed" label in one session, then present a summary table for user selection before merging. Use this skill when asked to "bulk review", "review all prs", "bprr", or "review unreviewed". |
Review all open pull requests at once for the awesome-quant curated list, then present a summary and merge selected PRs.
IMPORTANT: Always use GitHub MCP tools for all GitHub operations. Do not fall back to bash commands like gh or other tools — use the GitHub MCP interface exclusively.
Use github_list_pull_requests with state=open, sort=created, direction=asc, per_page=30 to get all open PRs.
Filter out PRs that have the "reviewed" label (these were already commented on and are waiting for contributor response).
Report the count:
Found X open PRs total, Y unreviewed (no "reviewed" label)
Use github_get_file_contents owner=wilsonfreitas, repo=awesome-quant, path=README.md to fetch current README once.
Cache this for all duplicate checks during review.
For each unreviewed PR, fetch in parallel:
github_get_pull_request for PR details (check mergeable status, labels)https://github.com/wilsonfreitas/awesome-quant/pull/{number}.diffThen validate each entry using the logic from review-pr skill:
Each entry MUST include one or more language tags and match one of these accepted formats:
Single language:
- [Project Name](https://github.com/owner/repo) - `Python` - Short description ending with a period.
Multiple languages:
- [Project Name](https://github.com/owner/repo) - `Python` `Rust` - Short description ending with a period.
Project with website and GitHub repo:
- [Project Name](https://project-site.com) - `Python` - Short description ending with a period. [GitHub](https://github.com/owner/repo)
CRAN project:
- [Package Name](https://cran.r-project.org/package=pkgname) - `R` - Short description ending with a period.
PyPI project:
- [package-name](https://pypi.org/project/package-name/) - `Python` - Short description ending with a period.
The core regex: ^\s*- \[(.*)\]\((.*)\) - (.*)$
Specifically check:
- (dash + space)[Name](URL)- (space, dash, space)`Python`) followed by -.[GitHub] link comes after the periodcran.r-project.org) acceptable for R packagespypi.org) acceptable for Python packages[GitHub] link in descriptionhttps://The README categories are:
Search the cached README for the project name and URL to ensure not already listed.
Format the results as:
## Bulk Review Summary
| # | Title | Author | Entries | Format | URL | Section | Duplicate | Verdict |
|---|-------|--------|---------|--------|-----|---------|-----------|---------|
| 335 | Apex Quant | sst19910323 | 1 | ISSUE | GitHub | Trading | No | NEEDS CHANGES |
| 336 | Alpha Skills | VernonOY | 1 | OK | GitHub | Factor | No | APPROVE |
...
For each PR, show:
After the table, ask:
Which PRs would you like to merge? (e.g., "336, 340" or "all approved")
Parse user response. Options:
If user asks about a specific PR, provide details before asking novamente.
For each PR to merge:
github_merge_pull_request with merge_method="squash"Note: Do NOT auto-merge without explicit user confirmation for each PR.
Reject immediately (close with polite comment) if:
For fixable issues (missing language tag, wrong section), comment and add "reviewed" label instead.
Key tools:
github_list_pull_requests - list open PRsgithub_get_pull_request - get PR detailsgithub_add_issue_comment - comment on PRgithub_merge_pull_request - merge PRgithub_update_issue - add label / close PRgithub_get_file_contents - fetch README for duplicate check
