Sashiko
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
3recommend
1warn against
Mar 18, 2026first mention
Oct 15, 2026latest mention
Why people recommend it
“The kernel now has AI tooling heavily integrated into patch review workflows as well with quite good results.”
“Sashiko is a great system”
Show 1 more
“I'm very glad they're not spamming the mailing list.”
Caveats and dissent
“on its Claude, Vertex and Gemini backends, a connection that drops mid-response is treated as a permanent error rather than retried.”
“done on an automated basis is a bad idea”
Threads where it came up
- Google Engineers Launch "Sashiko" for Agentic AI Code Review of the Linux Kernel 5 mentions
- Libreboot 26.10 "Ominous Olive" released with UEFI, Chromebook support 1 mention
- Why isn't the industry freaking out about DeepSeek 4.1 Flash? 1 mention
- Data-only attacks are easier than you think (2024) 1 mention
- Claude Opus 5.5 1 mention
Also written as sashiko. Data: sashiko.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 9
“The kernel now has AI tooling heavily integrated into patch review workflows as well with quite good results.”
“Sashiko is a great system”
“on its Claude, Vertex and Gemini backends, a connection that drops mid-response is treated as a permanent error rather than retried.”
“My prompts are moving in the other direction as sashiko”
Of course I specifically avoided invoking that language's name within the context of kernel programming in fear of summoning a Linus. And he's so right. I didn't think like that back then, but new/delete (which have to be overloaded for kernel) behind allocators behind containers, vtables, =0, uninitialized members, unhandled ctor errors, template magic, "sometimes rvo", compiler hints, "sometimes reinterpret cast",
“https://github.com/sashiko-dev/sashiko”
“I'm very glad they're not spamming the mailing list.”
No, it's reviewing patches posted on LKML and offering suggestions. The original patch posted corresponding to your link was this, which was (presumably!) written by a human: https://lkml.org/lkml/2026/3/9/1631
“done on an automated basis is a bad idea”