feat(skills): batch-review, a ranked review pass over a repository's open pull requests, one subagent each, code only #9
No reviewers
Labels
No labels
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Tooling!9
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Tooling:feat/batch-review-skill"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type: feat · Risk: low · Tested on: not run (a skill file and two doc lines) · Needs: none
Why
Open pull requests pile up faster than people can read them. A maintainer wants to say "review the top 20" and get the
PRs ranked by what matters to people, each read by its own reviewer, the small conflicts and nits fixed on the spot,
every review posted on the forge, and a report that shows plainly which PRs are ready for a human to merge. The steps
worked by hand over 60 PRs on 2026-11-15; this writes them down once for every MagicBeanDev repository.
It replaces Longshot's pull request 908, which put the same
skill in Longshot alone.
What changed
Adds the
batch-reviewskill (/magicbean:batch-review top 20,next 30,top 10 perf fixes), listed in AGENTS.md andthe README.
skills/batch-review/SKILL.md: ranks the open PRs (priority label, then what the change does for people, then howfinished it is; skips WIP and PRs already reviewed at their current head); one subagent per PR, code only, nothing
run; a reviewer fixes a basic conflict or nit in a workspace of its own and pushes it to the PR's branch, keeping the
author's commits (a suggestion in the review when the push is refused); posts one review with the verdict
docs/forge.md defines; then tables built from the forge's state: ready to merge, fixed and pushed, waiting on a test
run, needs the author, comments, duplicates and merge order, not reviewed. What a review checks against is each
repository's own AGENTS.md and CONTRIBUTING.md.
AGENTS.md,README.md: the skill in the task table and the skills list.Measurements
Nothing to measure: a skill file and two documentation lines.
Testing
Tested: the steps were followed by hand for review passes over 60 open Longshot PRs (reviews posted, fixes pushed,
tables built); this file is those steps written down.
Not tested:
/magicbean:batch-reviewas one command: it didn't exist until this file.Must be tested: None.
Risks
What could break: the skill has agents push fixes to other people's PR branches. It limits that to basic conflicts
and nits, keeps the author's commits, never changes behaviour or a design, and falls back to a suggestion in the review
when the push is refused.
Turning it off: revert the commit.
Compatibility: Nothing changes.
🤖 Generated with Claude Code