feat(skills): batch-review, a ranked review pass over a repository's open pull requests, one subagent each, code only #9

Merged
HumanBean merged 1 commit from HumanBean/Tooling:feat/batch-review-skill into main 2026-11-15 21:23:10 +00:00
Owner

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-review skill (/magicbean:batch-review top 20, next 30, top 10 perf fixes), listed in AGENTS.md and
the README.

  • skills/batch-review/SKILL.md: ranks the open PRs (priority label, then what the change does for people, then how
    finished 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-review as 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

**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](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/908), which put the same skill in Longshot alone. ## What changed Adds the `batch-review` skill (`/magicbean:batch-review top 20`, `next 30`, `top 10 perf fixes`), listed in AGENTS.md and the README. - `skills/batch-review/SKILL.md`: ranks the open PRs (priority label, then what the change does for people, then how finished 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-review` as 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](https://claude.com/claude-code)
HumanBean deleted branch feat/batch-review-skill 2026-11-15 21:23:10 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Tooling!9
No description provided.