WIP: feat(skills): batch-review, a review pass over the open pull requests: ranked, one subagent each, code only #908
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved @ 1697603
beanstalk: approved @ 2c5a62e
beanstalk: approved @ 4fd82b7
beanstalk: approved @ 64d6d09
beanstalk: approved @ 6f91fae
beanstalk: approved @ 70a78f9
beanstalk: approved @ 8015c9a
beanstalk: approved @ 8d361dc
beanstalk: approved @ 9d8356e
beanstalk: approved @ abf2227
beanstalk: approved @ d82f202
beanstalk: approved @ e5f1e40
beanstalk: approved @ ee8ab5f
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!908
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Longshot: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 in the game (a skill file and one line in AGENTS.md) · Needs: none
Why
Reviews pile up faster than people can read them: there were 265 open pull requests when this was written, and the
review pass over the top 30 took one long session to do by hand. A maintainer wants to say "review the top 20" and get
the PRs ranked by what matters to players, 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.
What changed
Adds the
batch-reviewskill (/batch-review top 20,/batch-review next 30,/batch-review top 10 perf fixes) anda pointer to it in AGENTS.md. The skill ranks the open PRs, runs one subagent per PR, and reports in tables.
.claude/skills/batch-review/SKILL.md:already reviewed at their current head, so "next 30" starts where the last pass ended. A re-review of a PR whose
author pushed since ranks high.
or a nit in a workspace of its own and pushes it to the PR's branch (a suggestion in the review when the push is
refused), then posts one review with the verdict docs/forge.md defines.
on a test run, needs the author, comments, duplicates and merge order, not reviewed.
AGENTS.md: one bullet pointing at the skill.Measurements
Nothing to measure: a skill file and one documentation line, no code the game runs.
Flags and settings
None.
Testing
Tested: the skill's steps were followed by hand for a review pass over 60 open PRs on 2026-11-15 (the reviews, the
fixes' push path and the tables); the file here is those steps written down for the team.
Not tested:
/batch-reviewitself as one command: the skill didn't exist as a command until this file.Must be tested: None.
Risks
What could break: the skill tells agents to push fixes to other people's PR branches. It limits that to basic
conflicts and nits, never a change in behaviour, a design or what a PR measured, and it falls back to a suggestion in
the review when the push is refused.
Turning it off: revert the commit.
Compatibility: Nothing changes.
Checklist
Everyone
type(scope): description) of the status line's type.main.python -I -B tests/run_all.pypasses (any failure that also fails onmainis named).third_party/untouched (a new folder with aPROVENANCE.mdinstead).When it applies
Assisted-by:/Co-Authored-By:trailers.🤖 Generated with Claude Code
Added a rule to the skill after the first pass: a reviewer keeps the author's commits when it rebases, and never squashes or rewrites their history for a nit.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.