jtljrdn/goodrepo

Agent Readiness

Agent ready

91/ 100

Quick scan · no AI34 checks run · 3 need a deep scan

Scores

The overall score is the average of these six

Open a category to see every check

›Discoverability75 / 85 points88

Can an agent quickly find the code that matters?

✓README.md at repository root+15
⚠README is thin (235 words), mostly a title and install line235 words · needs 300 words or more0 / 10
✓Source lives under folders an agent can guess (src, app, lib, workspaces)100% · needs 80% or more+15
✓Directory tree stays shallow (9 in 10 files within 5 levels)5 levels · limit 7 levels+15
✓Tests sit next to the code they cover100% · needs 60% or more+15
✓Build output is not committed+15

Biggest wins first

01
Document the database and migration workflow
High impactInstructions
This project talks to a database but nothing documents how to change the schema. Agents commonly hand-edit generated migration files when this is undocumented.
Add a Database section to AGENTS.md describing:
- —Where the schema is defined
- —The exact command that generates a migration
- —How migrations are applied locally and in CI
- —What must never be edited by hand
02
Expand the README
Low impactDiscoverability
The README is 235 words. It is the first file an agent reads.
Cover what the project does, how to run it, and where the main code lives.

Not available yet

An AI reads the code to settle the 3 checks a quick scan cannot. Takes about a minute and is free with a GitHub sign-in.