一键在 Manus 中运行任何 Skill

bprr

星标27,628

分支3,677

更新时间2026年6月29日 20:07

Bulk PR reviewer for awesome-quant. Use when the user asks to review all open PRs, review unreviewed PRs, bulk review, or mentions "bprr". Reviews open PRs lacking the reviewed label and presents a summary before any merge/comment/label action.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

wilsonfreitas

wilsonfreitas/awesome-quant

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

BPRR: Bulk PR Reviewer

Review multiple open pull requests for README entry contributions.

Hard Rules

Use GitHub MCP tools for PR operations. Do not use gh for PR review, comments, labels, closing, or merging.
Filter out PRs with the reviewed label unless the user asks to re-review them.
Do not comment, label, close, or merge until the user explicitly approves each action.
Do not auto-merge all approved PRs unless the user explicitly selects that option.
If GitHub MCP tools are unavailable, report the blocker and point to docs/codex-setup.md.

Workflow

List open PRs sorted oldest first.
Filter to unreviewed PRs by default.
Fetch the default-branch README.md once for duplicate checks.
For each PR, fetch details, labels, files, body, and diff.
Review only added README.md entries unless the PR changes other files; flag other file changes as unusual.
Validate each PR with the same checks as $sprr. Use scripts/validate_readme.py --diff-from <base-ref> when the PR branch is available locally; otherwise apply the validator's rules manually from the MCP diff.

Validation Checklist

For each added entry, check:

Parser regex match.
Required language tags for new non-commercial entries.
Description period before optional [GitHub](...).
https:// URLs.
Exact optional [GitHub](https://github.com/owner/repo) format.
Correct category section.
Commercial placement under Commercial & Proprietary Services.
Duplicate project names or URLs.
Activity, archived status, and basic documentation for GitHub repos.
Clear rationale for multiple related projects in one PR.

Summary Output

Present a table:

| PR | Title | Author | Entries | Format | URL | Section | Duplicate | Verdict |
|----|-------|--------|---------|--------|-----|---------|-----------|---------|

After the table, list any PRs that need detailed notes.

Ask what to do next. Accept selections like:

merge 123, 124
comment 125
close 126
all approved
none

Confirm each merge before executing it.

同仓库更多 Skills

同仓库

sprr

wilsonfreitas/awesome-quant

Single PR reviewer for awesome-quant. Use when the user asks to review, validate, comment on, label, close, or merge one specific pull request that adds README.md entries. Triggers include "sprr", "review PR", "check PR", and "validate contribution".

2026-06-2927.6k

update-pypi-dates

wilsonfreitas/awesome-quant

Refresh tracked PyPI last-updated dates in awesome-quant README.md. Use when the user asks to update PyPI dates, refresh PyPI metadata, or run update-pypi-dates.

2026-06-2927.6k

bprr

wilsonfreitas/awesome-quant

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".

2026-04-2527.6k

sprr

wilsonfreitas/awesome-quant

Single PR reviewer. Review and validate pull requests that add new library entries to the awesome-quant README.md. Use this skill whenever the user asks to review PRs, check contributions, validate submissions, triage pull requests, or mentions anything about incoming entries or additions to the curated list. Also triggers for "review pr", "check prs", "merge contributions", "sprr", or any PR-related workflow in this repo.

2026-04-2527.6k

update-pypi-dates

wilsonfreitas/awesome-quant

Check PyPI projects for last updated dates and update README.md entries. Use this skill to keep PyPI project information current with latest release dates from PyPI. Run periodically to maintain up-to-date metadata on Python packages listed in awesome-quant.

2026-03-2227.6k

name	bprr
description	Bulk PR reviewer for awesome-quant. Use when the user asks to review all open PRs, review unreviewed PRs, bulk review, or mentions "bprr". Reviews open PRs lacking the reviewed label and presents a summary before any merge/comment/label action.

BPRR: Bulk PR Reviewer

Review multiple open pull requests for README entry contributions.

Hard Rules

Use GitHub MCP tools for PR operations. Do not use gh for PR review, comments, labels, closing, or merging.
Filter out PRs with the reviewed label unless the user asks to re-review them.
Do not comment, label, close, or merge until the user explicitly approves each action.
Do not auto-merge all approved PRs unless the user explicitly selects that option.
If GitHub MCP tools are unavailable, report the blocker and point to docs/codex-setup.md.

Workflow

List open PRs sorted oldest first.
Filter to unreviewed PRs by default.
Fetch the default-branch README.md once for duplicate checks.
For each PR, fetch details, labels, files, body, and diff.
Review only added README.md entries unless the PR changes other files; flag other file changes as unusual.
Validate each PR with the same checks as $sprr. Use scripts/validate_readme.py --diff-from <base-ref> when the PR branch is available locally; otherwise apply the validator's rules manually from the MCP diff.

Validation Checklist

For each added entry, check:

Parser regex match.
Required language tags for new non-commercial entries.
Description period before optional [GitHub](...).
https:// URLs.
Exact optional [GitHub](https://github.com/owner/repo) format.
Correct category section.
Commercial placement under Commercial & Proprietary Services.
Duplicate project names or URLs.
Activity, archived status, and basic documentation for GitHub repos.
Clear rationale for multiple related projects in one PR.

Summary Output

Present a table:

| PR | Title | Author | Entries | Format | URL | Section | Duplicate | Verdict |
|----|-------|--------|---------|--------|-----|---------|-----------|---------|

After the table, list any PRs that need detailed notes.

Ask what to do next. Accept selections like:

merge 123, 124
comment 125
close 126
all approved
none

Confirm each merge before executing it.