On Fri, 13 Feb 2026 at 11:29, Chris Mason <[email protected]> wrote: > > On 2/11/26 2:44 PM, Dave Airlie wrote: > > Hi all, > > > > This came up at kernel maintainers summit, so I've been trying to see > > what I can piece together, and have a small demonstration that may be > > useful to some people. > > > > I didn't want to pollute the mailing list with AI patch reviews, so I > > decided to set up a public-inbox that the reviews are pushed into. > > This isn't currently automated, I'm just asking claude to pull the > > last 2-3 days of patches and review what is new every so often. > > > > The workflow use lei to pull mails to local PC, use review-prompts + > > my own prompt to try and review a patch series, both as a complete > > work, and per-patch reviews, then create the reply emails and put them > > into a public inbox git tree for publishing. > > > > I've no idea if it's using review-prompts properly or at all, this is > > all very vibe coded so far. > > Speaking of vibe coding, I took some commits with Fixes: tags and ran > them through claude to identify subsystem specific knowledge that would > make it more effective at reviewing. The results for drm are here: > > https://github.com/masoncl/review-prompts/blob/main/kernel/subsystem/drm.md > > I'm happy to adjust of course, this is just a basic starting point.
Oh interesting, I might try folding that into my prompts next week, I've written a blog post with what I've been doing https://airlied.blogspot.com/2026/02/drm-subsystem-ai-patch-review.html and a link to the current claude generated reviewer script and prompts I'm using. Dave.
