Leads the technical operations group, Rewind.
Explore with your AI assistant
ChatGPT (opens in a new tab)Claude (opens in a new tab)Perplexity (opens in a new tab)Grok (opens in a new tab)
Opens a new chat with a prompt that points the assistant to this archive. What it writes is its own, not the archive's: check any quotation on its passage page before you rely on it. Or add the archive to your assistant as a connector: https://the-ai-record.com/mcp (how).
Author bio on the Rewind blog: works at Rewind leading the technical operations group; earlier roles at Signiant and Nortel.
Why their word counts: Writes as the leader of the group that built and runs the Diff Vader reviewer, and says he reports its results to leadership and auditors.
Profile from this source, checked 2026-11-04.
We were merging on the order of forty PRs a day across our GitHub organizations, well over a thousand a month, and climbing.
Dave NorthLeads the technical operations group · Leader, 
Rewind
Post: Review is the bottleneck now: How we let AI approve pull requests (safely), Rewind blog, June 1, 2026, at Opening.
For the curious: reviews average around $0.73 per PR, with significant variance. Small dependency bumps cost cents; large multi-file PRs with many substantive findings can push past twelve dollars.
Dave NorthLeads the technical operations group · Leader, Rewind
Post: Review is the bottleneck now: How we let AI approve pull requests (safely), Rewind blog, June 1, 2026, at The Death Star.
Auto-approve is not auto-merge. When Diff Vader approves, it posts an APPROVE review, the same thing a human reviewer clicking “approve” does. It does not push the merge button. The engineer merges (or GitHub’s native auto-merge does, if they enabled it), and every existing gate—CI, branch protection, required-reviewer counts—still applies.
Dave NorthLeads the technical operations group · Leader, Rewind
Post: Review is the bottleneck now: How we let AI approve pull requests (safely), Rewind blog, June 1, 2026, at What an engineer actually sees.
Diff Vader and the Death Star were built almost entirely with Claude Code, but not by typing “build me an AI reviewer” and shipping whatever came back. We used spec-based development — Superpowers for the core methodology, augmented with our own skills — which forces every piece of work through brainstorm → written spec → reviewed implementation plan → execution → code review, with discrete human checkpoints in between.
Dave NorthLeads the technical operations group · Leader, Rewind
Post: Review is the bottleneck now: How we let AI approve pull requests (safely), Rewind blog, June 1, 2026, at What I’d tell another engineering leader.
So we built a system that fixes the allocation. It’s called Diff Vader: an AI reviewer that looks at every PR across our orgs and, for a carefully bounded set of low-risk changes, becomes the only reviewer needed, freeing human reviewers to spend their judgment where judgment actually matters.
Dave NorthLeads the technical operations group · Leader, Rewind
Post: Review is the bottleneck now: How we let AI approve pull requests (safely), Rewind blog, June 1, 2026, at Opening.
It declares the hard rules the verdict engine is not allowed to override no matter what the council says: paths that touch authentication, authorization, secrets, encryption, and anything that changes who is allowed to approve future changes always require a human.
Dave NorthLeads the technical operations group · Leader, Rewind
Post: Review is the bottleneck now: How we let AI approve pull requests (safely), Rewind blog, June 1, 2026, at The council: many specialists, one question.