WF16 / Build / Keep watch
Keep a pull-request queue from quietly getting stuck
Review CI, dependencies, and outstanding feedback, then report the next useful action for each pull request.
Make it yoursSee the sampleTHE WAY THROUGH
From your material to a useful result.
- 01
Identify the exact head commit, required checks, reviews, and dependencies for each open pull request.
- 02
Classify blocked, ready for review, and apparently ready to merge using current evidence.
- 03
Suggest the smallest next step and report only new or changed blockers.
- 04
Before any approved mutation, refresh the head and required checks. Follow repository protections; record the resulting commit or action.
A FICTIONAL TASK TO PRACTICE ON
Here’s the job.
Fictional PR #12: current head bbb222; required build succeeded on aaa111; review approved on bbb222; no build result for bbb222. PR #13: head ccc333; build passed on ccc333; required reviewer has not responded.
What a careful result should contain
#12: blocked — current head lacks a required build result. #13: blocked — required review is missing. No merge-ready PRs and no repository mutations.
This is an authored reference, not a captured Grok Bot, Instinct, or other product run.
BEFORE YOU RELY ON IT
Give the result a proper check.
- A green check on an old commit does not validate the current head.
- A missing required review remains a blocker.
- Read-only monitoring never silently rebases or merges.
Try to break it
The head changes after the report. Pass: re-read the new head and checks before proposing a merge. Fail: use the previous green status.
TAKE IT FOR A SPIN
Bring your own details.
Describe your task and paste the source material you want to use. This page prepares a prompt; your chosen AI tool does the work.
These details stay in this page until you copy them. They are not saved or sent to a model here.
Read the full starting instructions
Audit this PR queue against the supplied repository rules. Tie every check and review to the relevant head commit, identify dependencies, and return current blockers with source links. Separate verified state from assumptions. For monitoring, deduplicate unchanged alerts and report access gaps. Do not merge, rebase, close, change code, or message others without appropriate authorization; refresh state before any approved mutation.