| name | request-re-review |
| description | Push changes on the current PR branch and request a fleet re-review. Use when the user says "request re-review", "push and re-review", "push for re-review", "I'm done with this PR have the fleet re-review", or "update PR and get it reviewed again". Also useful when the user has manually edited a PR branch in any pane and wants the fleet review pipeline to pick it back up. |
request-re-review
Preconditions
- You are on a PR branch (not a scratch branch, not master).
- There is an open PR for this branch.
gh is authenticated.
Flow
1. Identify the current PR
git branch --show-current
Find the open PR for this branch:
gh pr list --state open --head <branch-name> --json number,title,labels
If no PR is found, tell the user and stop.
2. Commit and push any pending changes
Invoke the commit-and-push skill to stage, commit, and push any
uncommitted changes on this branch. If the working tree is already
clean and all commits are pushed, skip to step 3.
3. Swap labels to request re-review
Remove stale fleet verdict labels and add the re-review request:
gh pr edit <N> --remove-label "fleet:approved" --remove-label "fleet:needs-fix" --remove-label "fleet:blocker" --add-label "human:re-review"
4. Post a comment
gh pr comment <N> --body "Human made changes — re-review requested."
5. Release the branch
Invoke the start-next-task skill to reset to a scratch branch off
origin/master. This frees the PR branch so reviewers (or other
agents) can check it out.
6. Report back
Print:
Re-review requested for PR #<N> (<title>).
- Label: human:re-review added, fleet:approved removed
- Branch released — reviewers can check it out
- Next reviewer pass will pick it up
Anti-patterns
- Leaving the PR branch checked out after requesting re-review.
The whole point is to release it for reviewers.
- Using this on a PR that's still
fleet:wip — that PR isn't
ready for review at all. Tell the user to finalize first.
- Force-pushing. Never
--force.
