Repository readiness
Every check
Explore the checks behind the readiness score, how each one helps a coding agent, and what its create-only fix can generate.
14 checks
- package-manager-lockfilesetup
Package manager lockfile
A matching lockfile lets an agent install reproducible dependencies.
Weight 5
- env-examplesetup
Environment variable example
An environment example tells an agent which local configuration values the project needs.
Weight 3
- node-version-pinnedsetup
Node.js version pinned
A declared Node.js version prevents agents from using an incompatible runtime.
Weight 3
- test-scriptverification
Test script
A test script gives an agent a reliable way to validate code changes.
Weight 5
- tests-passverification
Tests pass
Passing tests help an agent avoid introducing regressions.
Weight 5
- build-scriptverification
Build script
A build command lets an agent validate production compilation.
Weight 4
- tests-existverification
Test files exist
Existing tests give an agent a safety net for changes.
Weight 4
- lint-scriptverification
Lint script
A lint command lets an agent detect common code-quality problems.
Weight 3
- typecheck-scriptverification
Typecheck script
Type checking catches errors that tests may not cover.
Weight 3
- install-documenteddocs
Installation documented
Documented installation steps let an agent set up the repository reliably.
Weight 4
- contributing-or-agents-docdocs
Contributor or agent guidance
Contributor instructions explain how an agent should work in the repository.
Weight 2
- ci-confighygiene
Continuous integration config
Continuous integration gives an agent a repeatable way to verify repository changes.
Weight 3
- formatter-confighygiene
Formatter configuration
A formatter configuration keeps agent-authored code consistent with the project.
Weight 2
- gitignore-sanehygiene
Useful .gitignore
Ignoring dependencies and generated outputs keeps agent changes focused on source files.
Weight 2