---
name: quick-review
description: >
  Review and accept/reject completed builds.
  Use when the user says /quick-review, "review builds", "accept reviews",
  "check reviews", or after completing a batch of builds.
invocable: true
---

# /quick-review — Review Completed Builds

Check for builds pending review and process them.

## Steps

1. **Run `review_list`** — shows tasks that are In Review with their build reports.

2. **If no tasks are pending review**, tell the user: "No builds pending review." Suggest the next action (build more tasks, or release if all are done).

3. **For each task pending review**, show:
   - Task ID and title
   - Effort (estimated vs actual)
   - Scope accuracy
   - Surprises or discovered issues
   - Brief summary of what was built

4. **Ask the user:** "Accept all N reviews, or review individually?"

5. **On acceptance, run `review_submit`** for each task with verdict "accept". Include a brief comment summarising the build.

6. **After all reviews are processed**, check if the sprint is complete:
   - If all sprint tasks are Done: "Sprint complete. Run `release` to merge and tag."
   - If tasks remain: "N tasks still to build. Use `/next-task` to continue."

## Notes

- If the user wants to reject or request changes on a specific task, run `review_submit` with the appropriate verdict and comments.
- Reviews are lightweight — the build report has the details. The user just needs to confirm the work is acceptable.