What the X-ray looks for
A coding agent only reads what is in the repo. So does whoever starts on Monday. Repo X-ray looks for eighteen files and signals that decide whether a repo can be understood, built and trusted without asking anyone — and shows what it looked for, so every cross can be fixed in minutes.
Eighteen checks in four groups:
- Onboarding — a README, an instruction file for agents (AGENTS.md, CLAUDE.md or equivalent), CONTRIBUTING, .editorconfig and a devcontainer.
- Reproducible build — a dependency lockfile, a Dockerfile or compose file, a task runner such as a Makefile, justfile or package.json, and pinned tool versions.
- Checks & automation — CI configuration, pre-commit hooks, Dependabot or Renovate, CODEOWNERS and a pull request template.
- Pulse — a licence, a push within the last 90 days, no open pull request older than 30 days, and a repo that is not archived.
Each check scores one point of eighteen. From 14 the repo is healthy: what is missing is polish. Between 9 and 13 it is under observation — the basics are there, but there are gaps an agent or a new colleague will guess their way around. Below 9 it is a referral: most of what makes a repo self-explanatory is missing, which says nothing about the code, only about how much it demands of whoever arrives new.
The tool makes four calls straight from your browser to GitHub’s public API and reads only the root directory and .github/ on the default branch. Nothing is sent to us and nothing is stored. If AGENTS.md is missing, the AGENTS.md generator is the next step; if CI is missing, it is Delivery Engineering.