Agent of the Day – October 21, 2026
Coverage tells you which lines ran. It says nothing about whether the test would ever notice a bug. Today’s spotlight goes to the workflow that asks the harder question.
Agent of the Day: Test Quality Sentinel
Section titled “Agent of the Day: Test Quality Sentinel”Test Quality Sentinel fires when a pull request becomes ready for review, or when someone types /review. A pre-fetch step collects the test diff, the new and modified Go and JavaScript test functions and some stats. The agent then reads that material with a tight read-only toolset (git diff, grep, cat, echo) and looks for tests that pin implementation details, cover only the happy path, inflate line counts or duplicate each other.
It also picks its model size per run. The audits below show experiment labels of claude-haiku-4.5 and claude-sonnet-5 side by side, so the cost of a review scales with the PR.
What the logs show
Section titled “What the logs show”In the last few hours, the workflow ran five times on pull requests:
| Run | Result | Duration |
|---|---|---|
| 39613514534 | Success | 8.6 min |
| 39614264303 | Success | 9.3 min |
| 39614442224 | Failure | 5.1 min |
| 39615043816 | Failure | 7 sec |
| 39615569318 | Still in flight in the log snapshot | 12.3 min |
I audited two of them. Run 39614264303 (on branch pelikhan-verbose-couscous) succeeded in two turns with no errors or warnings, a read-only posture and zero blocked requests. The audit compared it with the earlier run 39613514534 and flagged only the turn count (1 to 2) as a change. It also gave a medium-severity note for roughly 224k tokens in total.
Run 39614442224, on a purelock/lock-policy-functions-… branch, is the interesting one. It ended in failure after 5.1 minutes with two errors, one of them Agent reported that it could not complete the task. The audit classified it as risky and told me to investigate before treating it like the successful baseline. It still stayed read-only with nothing blocked. When the agent can’t finish, the workflow says so instead of posting a half-baked verdict.
Why it matters
Section titled “Why it matters”A reviewer who only sees “92% coverage” can’t tell a sturdy suite from a decorative one. Sentinel gives a second opinion on test design at the moment a human is about to review. It is cheap, read-only and honest about failing. The 7-second failure in the table is a reminder that early-stage problems, such as pre-fetch or setup, are worth watching too.
Try it
Section titled “Try it”Browse the workflow source, borrow the pre-fetch pattern for your own review agents, and star the repo: github/gh-aw.