Running the pre-flight inspection…
Running the pre-flight inspection…
Agent-Ready Score
58/100Conditional clearance
[](https://sortielabs.com/score/react/react)
Agent rules file7/15
Found CLAUDE.md but no AGENTS.md — only some tools will pick these up.
FIX → Add an AGENTS.md at the root: architecture map, hard rules, and how to verify changes.
Rules have substance4/8
Your rules file is very thin — a couple of lines won't steer anything.
FIX → Write real working rules: what to never touch, what to run after every change, where things live.
Cross-tool coverage0/7
Only one (or zero) agent tools are catered for.
FIX → Add a one-line CLAUDE.md that imports AGENTS.md (`@AGENTS.md`) so every tool reads the same rules.
CI pipeline10/10
GitHub Actions workflows found — agents' mistakes get caught.
Tests exist8/8
Test files found — agents can prove their changes work.
Score another repo
One-command verify0/7
No verify, check, lint or typecheck entry point found.
FIX → Add `scripts/verify.sh` (typecheck + lint + build + test) and require it in your agent rules.
Env template0/7
No .env.example found.
FIX → Ship a .env.example so agents (and humans) know what config exists without seeing values.
.gitignore5/5
Present.
Lockfile committed4/4
Dependencies are pinned — reproducible installs.
License4/4
Present.
README8/8
A real README exists.
Contributing guide4/4
Present.
Docs directory0/3
No docs/ directory.
FIX → A docs/ folder gives agents somewhere to look before inventing answers.
Typed foundations4/10
JavaScript without TypeScript config — agents get no type safety net.
FIX → Typed languages (or strict TS config) catch agent mistakes before runtime.