We prepare your codebase so AI writes 90% of the code.
RepoPrime audits 10 categories, scores your repo 0–100 for Agent-Readiness, and ships a fix playbook per finding that your AI agent can execute directly.
↑ runs locally · never uploads source · writes only under .repoprime/
02the problem
Your AI agent is only as good as the context you give it.
◆ ETH Zürich, 2025
# AGENTS.md
This is a TypeScript project.
Run tests with npm test.
Follow best practices.
↳ score: 14/100 · worse than empty
Generic AGENTS.md makes your agent WORSE
A study comparing Claude Code output with generic AGENTS.md ("this is a TypeScript project") vs. no AGENTS.md at all found the generic instructions materially degraded task success. Boilerplate context is not neutral — it crowds out the specific intent the agent actually needs.
◆ what we see
✗ wildcard CORS in 3 handlers
✗ 14 undocumented env vars
▲ 7 deps pinned to ^
▲ process.env accessed 41×
✗ 0 migrations committed
Bugs agents silently reproduce
Undocumented env vars. Wildcard deps. Missing migrations. Unvalidated process.env. Wildcard CORS. Your agent has no way to see these are mistakes — so when it writes the next handler, it copies the pattern, and the bug propagates.
◆ tooling gap
ESLintcode for humans
SonarQubecode for humans
CodeClimatecode for humans
Copilotreads · does not score
Cursorreads · does not score
RepoPrimecontext for agents
ESLint and Sonar score code for humans
They catch unused variables, cognitive complexity, test coverage. None of them grade the context files your AI agent reads before writing a line. Until now, repo quality for agents was invisible.
03how it works
Three steps. One command. Zero mutations to your source.
One command. Ten analyzers. Seventy rules.
Runs locally on your machine. Reads your repo, never writes to source files. Produces report.json and updates your AGENTS.md in-place if allowed.
API version prefix, validation pipe, rate limiter, contract tests.
4 rules75% fixable
05playbook demo
Every finding ships a playbook your agent can run.
Click a finding on the left to see its rendered .repoprime/fixes/<fixerId>.md. The Prompt for your agent block is exactly what goes to Claude Code or Cursor.
~/acme-api ❯ repoprime scan . --fixable
◇ 49 fixable findings across 10 analyzers · showing top 3
→ wrote .repoprime/fixes/security.fix-cors.md
~/acme-api ❯
.repoprime/fixes/security.fix-cors.md
Fix: security.fix-cors
severity: high · location: src/main.ts:14 · auto-fixable
## Context
CORS is currently `origin: true` — any origin passes preflight. Exposes browser clients to CSRF on authenticated endpoints. ETH Zurich research shows generic fixes (`cors(...)`) degrade agent output vs. no config at all.
## Files affected
→src/main.ts
→.env.example
→README.md
## Prompt for your agent
Restrict Nest CORS to an allow-list read from CORS_ORIGINS env.
Remove the wildcard `origin: true` and reject non-listed origins.
Add CORS_ORIGINS=<your allowed production origin> to .env.example.
Verify by running `curl -I` against the /health endpoint with a disallowed Origin header
and confirm the Access-Control-Allow-Origin header is NOT echoed back.