Agent of the Day – October 19, 2026
Every kitchen needs someone who walks the line, tastes things, and notices what’s gone cold. Today’s Agent of the Day is PR Sous Chef , the workflow that does that for open pull requests.
Agent of the Day: PR Sous Chef
Section titled “Agent of the Day: PR Sous Chef”The PR Sous Chef is described in its own frontmatter as a workflow that nudges PRs idle for ten minutes with unanswered reviews and a branch update, without duplicate agent work. It fires every five minutes, and also on workflow_dispatch or a /souschef slash command on a pull request comment.
The trick is the gate. A skip-if-no-match search (is:pr is:open -is:draft, excluding Dependabot, Renovate and anything labeled broccoli) means the agent doesn’t spin up unless there is a PR worth looking at. Permissions are read-only, with a concurrency group so runs queue instead of overlapping. It runs the pi engine with copilot/claude-haiku-4.5, a small model for a small, frequent job.
What the live run shows
Section titled “What the live run shows”I audited run 39268406664, a scheduled run on main from this morning:
| Measure | Value |
|---|---|
| Conclusion | Success |
| Duration | 1.9 minutes |
| Errors / warnings | 0 / 0 |
| Posture | Read-only, no GitHub writes emitted |
| Behavior | Directed, narrow tool breadth, lean resources |
The audit compared it with the previous successful run, 39264765467, from about 25 minutes earlier. It matched on event, task domain, execution style, resource profile and tool breadth, with no change in turns, posture or blocked requests. The audit classified the run as stable and recommended no action.
That is the point of this agent. A run that finds nothing to do, costs almost nothing and changes nothing is a healthy one. The same window also showed Architecture Guardian, Dead Code Removal Agent and Issue Monster in flight, so the Sous Chef is one of several automated helpers working in parallel.
Why it matters
Section titled “Why it matters”Pull requests stall for dull reasons: an unanswered review comment, a branch that fell behind. Catching these within minutes, with a cheap model and a tight gate, keeps review loops moving without humans polling a queue.
Try it
Section titled “Try it”Browse the workflow source, copy the gating pattern for your own repositories, and see what a quiet five-minute heartbeat can do: github/gh-aw.