The latest articles on DEV Community by Sherv Nariman (@shervnariman). https://dev.to/shervnariman https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4020033%2F5234a65b-5939-4f57-aa5c-bc8da470d25e.jpg https://dev.to/shervnariman en Sherv Nariman Tue, 07 Jul 2026 18:12:31 +0000 https://dev.to/shervnariman/i-built-a-lightweight-cli-to-catch-risky-ai-assisted-code-patterns-before-pr-review-27ih https://dev.to/shervnariman/i-built-a-lightweight-cli-to-catch-risky-ai-assisted-code-patterns-before-pr-review-27ih <p>AI coding tools are great at producing working-looking patches. But after using them more, I noticed a recurring problem: the code can look done while the diff still hides review debt.</p> <p>I built SlopCheck as a small local CLI to scan git diffs for obvious risky patterns before review.</p> <p>Try it:</p> <p>npx <a class="mentioned-user" href="https://dev.to/shervnariman">@shervnariman</a>/slopcheck diff</p> <p>I’m especially looking for feedback on what rules should be added next.</p> ai cli javascript showdev