<?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: Moteeb Asad</title>
    <description>The latest articles on DEV Community by Moteeb Asad (@moteebasad).</description>
    <link>https://dev.to/moteebasad</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%2F4245417%2F8c6e3e19-86ef-4d25-8f11-ac6dbf3c4ffd.png</url>
      <title>DEV Community: Moteeb Asad</title>
      <link>https://dev.to/moteebasad</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/moteebasad"/>
    <language>en</language>
    <item>
      <title>AI writes the code fast. The repo is where it shows.</title>
      <dc:creator>Moteeb Asad</dc:creator>
      <pubDate>Tue, 17 Nov 2026 11:31:06 +0000</pubDate>
      <link>https://dev.to/moteebasad/ai-writes-the-code-fast-the-repo-is-where-it-shows-6oh</link>
      <guid>https://dev.to/moteebasad/ai-writes-the-code-fast-the-repo-is-where-it-shows-6oh</guid>
      <description>&lt;p&gt;A lot of repos shared on LinkedIn look the same now. The app works, the demo is clean, but open the repo and it tells another story: everything pushed straight to &lt;code&gt;main&lt;/code&gt;, 200 commits called "update", one commit that changes 40 files, no README, and sometimes a &lt;code&gt;.env&lt;/code&gt; sitting in the history.&lt;/p&gt;

&lt;p&gt;The app is fine. The repo says nobody is maintaining it.&lt;/p&gt;

&lt;p&gt;With AI writing so much of the code, this matters more than before. When you ask a tool for a feature, it can change ten files at once. Some of those changes you asked for. Some you didn't. The repo is the only place someone can see whether you checked.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why I built it&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A few weeks back I kept seeing the same thing on LinkedIn: people shipping real apps with AI, proud of them, and the repo behind them was a mess. Not because they’re bad developers. Nobody showed them the repo part. The tools teach you to build. They don’t teach you to protect main or keep a key out of the history.&lt;/p&gt;

&lt;p&gt;So I wrote a blog post about it: the habits that keep a repo in a state someone else can trust. Protect main, one short branch per change, a pull request for every change, CI, clear commits, no secrets, a real README. You can read it here: &lt;a href="https://moteebasad.dev/blog/keep-your-repo-healthy-when-ai-writes-the-code" rel="noopener noreferrer"&gt;Keep your repo healthy when AI writes the code&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;A post is a start, but nobody goes through a checklist by hand. I wanted one command that does it for you. So I built check-repo-ready.&lt;/p&gt;

&lt;h2&gt;
  
  
  check-repo-ready
&lt;/h2&gt;

&lt;p&gt;It reads your repo and tells you what's missing. It only reads. It never changes anything.&lt;br&gt;
&lt;/p&gt;

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

&lt;/div&gt;



&lt;p&gt;Here is a real run on one of my projects, before I cleaned it up:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;check-repo-ready  nortecaca-platform

Branches
  ✗ branch-protection   main: not protected, anyone can push to it
                        develop: not protected, anyone can push to it

CI
  ✓ ci-on-pr            .github/workflows/ci.yml

Secrets
  ✓ env-tracked         no .env file is tracked
  ✓ env-in-history      no .env file in git history
  ✓ env-example         backend/.env.example

README
  ✗ readme              no README at the repo root

2 problems, 0 warnings
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two real problems. &lt;code&gt;main&lt;/code&gt; had no protection, so anything could be pushed straight to it. And the README was in &lt;code&gt;frontend/&lt;/code&gt;, not the root, so GitHub's repo page showed nothing to a visitor.&lt;/p&gt;

&lt;p&gt;Here is the tool run on its own repo, after the work is done:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;check-repo-ready  repo-ready (main)

Branches
  ✓ main                pull request and passing CI required
  ✓ develop             pull request and passing CI required

CI
  ✓ ci-on-pr            .github/workflows/ci.yml

History
  ✓ commit-messages     all 43 recent commits say what changed
  ✓ direct-pushes       all 7 commits on main came through pull requests

Secrets
  ✓ env-tracked         no .env file is tracked
  ✓ env-in-history      no .env file in git history
  ✓ secrets-in-code     no secrets in tracked files
  ✓ secrets-logged      no secrets written to logs
  ✓ env-example         not needed: the code reads no project env variables

README
  ✓ readme              README.md has setup or run steps

0 problems, 0 warnings
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What it checks
&lt;/h2&gt;

&lt;p&gt;Ten checks right now: branch protection on &lt;code&gt;main&lt;/code&gt; and &lt;code&gt;develop&lt;/code&gt;, CI running on pull requests, commit messages, direct pushes to &lt;code&gt;main&lt;/code&gt;, &lt;code&gt;.env&lt;/code&gt; files that are tracked or in the history, leaked keys in the code or the logs, a &lt;code&gt;.env.example&lt;/code&gt;, and whether the README tells you how to run the project.&lt;/p&gt;

&lt;p&gt;It reads branch rules through the GitHub API and scans the git history on your machine. It never prints a secret value. If a key is already in your history, it tells you to rotate it, because removing the file does not make a leaked key safe again.&lt;/p&gt;

&lt;h2&gt;
  
  
  Not the same as other tools
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/itxashancode/gh-repo-health" rel="noopener noreferrer"&gt;gh-repo-health&lt;/a&gt; and &lt;a href="https://github.com/todogroup/repolinter" rel="noopener noreferrer"&gt;repolinter&lt;/a&gt; check community files: LICENSE, CONTRIBUTING, CODE_OF_CONDUCT. Good things to have. check-repo-ready looks at a different thing: how the repo is maintained. Protection, CI, secrets, history.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it on your repo
&lt;/h2&gt;

&lt;p&gt;Run it inside any project:&lt;br&gt;
&lt;/p&gt;

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

&lt;/div&gt;



&lt;p&gt;It needs Node 22.12 or newer and git. The branch-protection check uses your GitHub CLI login if you have one; without it, that one check is skipped and the rest still run.&lt;/p&gt;

&lt;p&gt;It's early (0.x), so the checks and output may still change. If you run it, reply with what it caught. Wrong calls and missing checks are exactly what I want to hear.&lt;/p&gt;

&lt;p&gt;Code: &lt;a href="https://github.com/moteeb-asad/repo-ready" rel="noopener noreferrer"&gt;github.com/moteeb-asad/repo-ready&lt;/a&gt;&lt;/p&gt;

</description>
      <category>github</category>
      <category>node</category>
      <category>ai</category>
      <category>devtool</category>
    </item>
  </channel>
</rss>
