DEV Community

Moteeb Asad
Moteeb Asad

Posted on

AI writes the code fast. The repo is where it shows.

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 main, 200 commits called "update", one commit that changes 40 files, no README, and sometimes a .env sitting in the history.

The app is fine. The repo says nobody is maintaining it.

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.

Why I built it

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.

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: Keep your repo healthy when AI writes the code.

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.

check-repo-ready

It reads your repo and tells you what's missing. It only reads. It never changes anything.

npx check-repo-ready
Enter fullscreen mode Exit fullscreen mode

Here is a real run on one of my projects, before I cleaned it up:

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
Enter fullscreen mode Exit fullscreen mode

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

Here is the tool run on its own repo, after the work is done:

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
Enter fullscreen mode Exit fullscreen mode

What it checks

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

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.

Not the same as other tools

gh-repo-health and repolinter 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.

Try it on your repo

Run it inside any project:

npx check-repo-ready
Enter fullscreen mode Exit fullscreen mode

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.

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.

Code: github.com/moteeb-asad/repo-ready

Top comments (0)