<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Subhan Ahmed</title>
    <description>The latest articles on DEV Community by Subhan Ahmed (@subhan_ahmed).</description>
    <link>https://dev.to/subhan_ahmed</link>
    <image>
      <url>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%2F4114467%2Ff8582654-cc71-45e1-a7f0-1261375b8531.jpg</url>
      <title>DEV Community: Subhan Ahmed</title>
      <link>https://dev.to/subhan_ahmed</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/subhan_ahmed"/>
    <language>en</language>
    <item>
      <title>I made a tiny CLI to sanity-check AI-written PR diffs</title>
      <dc:creator>Subhan Ahmed</dc:creator>
      <pubDate>Tue, 08 Sep 2026 20:34:19 +0000</pubDate>
      <link>https://dev.to/subhan_ahmed/i-made-a-tiny-cli-to-sanity-check-ai-written-pr-diffs-3464</link>
      <guid>https://dev.to/subhan_ahmed/i-made-a-tiny-cli-to-sanity-check-ai-written-pr-diffs-3464</guid>
      <description>&lt;p&gt;I keep seeing AI-written PRs that look fine at first glance, but the risky parts are buried in the diff.&lt;/p&gt;

&lt;p&gt;So I made Agent Diff Sentinel, a small open-source CLI that scans a git diff and points reviewers to the stuff worth checking first:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;auth, billing, security, database, CI, and dependency changes&lt;/li&gt;
&lt;li&gt;secret-looking added lines&lt;/li&gt;
&lt;li&gt;missing tests&lt;/li&gt;
&lt;li&gt;oversized generated-looking files&lt;/li&gt;
&lt;li&gt;TODO/FIXME/hack markers&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It can output plain text, JSON, or Markdown, and it can fail CI on high-risk findings.&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/subhanA-UA/agent-diff-sentinel" rel="noopener noreferrer"&gt;https://github.com/subhanA-UA/agent-diff-sentinel&lt;/a&gt;&lt;br&gt;
Live page: &lt;a href="https://subhana-ua.github.io/agent-diff-sentinel/" rel="noopener noreferrer"&gt;https://subhana-ua.github.io/agent-diff-sentinel/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d love feedback from people using Codex, Cursor, Claude Code, or similar tools on real repos: what diff checks would you want before trusting an AI-assisted PR?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>cli</category>
      <category>git</category>
      <category>security</category>
    </item>
    <item>
      <title>Make your repo ready for AI coding agents in one command</title>
      <dc:creator>Subhan Ahmed</dc:creator>
      <pubDate>Mon, 07 Sep 2026 18:57:54 +0000</pubDate>
      <link>https://dev.to/subhan_ahmed/make-your-repo-ready-for-ai-coding-agents-in-one-command-3e50</link>
      <guid>https://dev.to/subhan_ahmed/make-your-repo-ready-for-ai-coding-agents-in-one-command-3e50</guid>
      <description>&lt;p&gt;I built &lt;strong&gt;Agent Ready Kit&lt;/strong&gt;, a small open-source CLI for one question that keeps showing up in AI-assisted development:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Can an AI coding agent actually understand and change this repo without wasting the first 20 minutes guessing?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The tool audits a repository locally and gives it an agent-readiness score. It checks the boring-but-important things that make agents useful instead of chaotic:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;clear README and install/run instructions&lt;/li&gt;
&lt;li&gt;test command discovery&lt;/li&gt;
&lt;li&gt;CI/workflow setup&lt;/li&gt;
&lt;li&gt;license and contribution basics&lt;/li&gt;
&lt;li&gt;env examples&lt;/li&gt;
&lt;li&gt;issue templates&lt;/li&gt;
&lt;li&gt;docs/examples&lt;/li&gt;
&lt;li&gt;AGENTS.md or other agent instructions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It can also generate a starter AGENTS.md so the next coding session has a better map of the project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I made it
&lt;/h2&gt;

&lt;p&gt;A lot of repos are technically open source but not very agent-friendly. Humans can infer missing setup steps from experience; agents usually burn tokens, make guesses, or ask for context that could have been written down once.&lt;/p&gt;

&lt;p&gt;I wanted a quick pre-flight check before handing a repo to Codex, Claude Code, Cursor, Copilot, Gemini CLI, or any other coding agent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/subhanA-UA/agent-ready-kit" rel="noopener noreferrer"&gt;https://github.com/subhanA-UA/agent-ready-kit&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Live page: &lt;a href="https://subhana-ua.github.io/agent-ready-kit/" rel="noopener noreferrer"&gt;https://subhana-ua.github.io/agent-ready-kit/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx agent-ready-kit
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What I want feedback on
&lt;/h2&gt;

&lt;p&gt;If you use AI coding agents in real repos, I would love feedback on what the score should include next.&lt;/p&gt;

&lt;p&gt;The next checks I am considering:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;package manager lockfile consistency&lt;/li&gt;
&lt;li&gt;flaky or missing test detection&lt;/li&gt;
&lt;li&gt;stale docs vs current scripts&lt;/li&gt;
&lt;li&gt;repo-specific agent safety rules&lt;/li&gt;
&lt;li&gt;PR-review readiness&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If this saves you a setup pass, or if the scoring misses something important, tell me. That feedback is more useful than a vague launch post.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>devtools</category>
      <category>ai</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
