Report · marked 10 Oct 2026
colbymchenry/codegraph
Solid foundations, held back in a few specific places.
C · 73,657 stars · 1,437 files · branch main
82
/100
A-
Instructions
25/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup
16/18Whether an agent can install the project and get it running without a human. Losing marks on environment config.Verification loop
19/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on lint and format rules.Context economy
11/20Whether the repo fits in a context window, or fights it. Losing marks on no committed build output and file sizes fit in context.Navigability
9/10How quickly anything new can orient itself. Losing marks on repository description.
Higher is better. Accent marks what is costing you most.
Fix these first
01
File sizes fit in context
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
02
Lint and format rules
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
03
No committed build output
Add these to .gitignore and `git rm -r --cached` them. Generated files pollute search results, so an agent grepping for a function finds the compiled copy and edits the wrong file.
The full marking
Every deduction below names the file or setting it came from.
Instructions 25/27 A+
Whether the repo tells an agent how to behave before it starts guessing.
✓Agent instruction file
12/12
AGENTS.md is present, which is the format the most tools read.
Also found: CLAUDE.md
✗Instruction quality
10/12
Specific enough that an agent can act on it.
Worth fixing: it's 38k characters, which burns context on every single turn.
names the actual commands to run
uses headings, so an agent can skim it
includes copyable code blocks
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 16/18 A
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
package-lock.json pins the dependency tree.
Found package-lock.json
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
package.json scripts (build, build:ui, build:lib, preuninstall, copy-assets, dev…)
scripts/ directory
✗Environment config
2/4
Env vars are mentioned in the README but there's no example file to copy.
Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.
✓Pinned runtime version
2/2
The language runtime version is pinned.
package.json engines.node >=20.0.0 <25.0.0
–Reproducible environment
n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 19/22 A
Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.
✓Tests exist
8/8
699 test files against 1196 source files.
e.g. __tests__/adaptive-explore-sizing.test.ts, __tests__/alias-binding-resolution.test.ts, __tests__/android-res-exclusion.test.ts
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
2 GitHub Actions workflows define what "passing" means.
✗Lint and format rules
0/3
No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
–Static type checking
n/a
Not applicable — the C compiler type checks every build.
Context economy 11/20 B-
Whether the repo fits in a context window, or fights it.
✗No committed build output
3/6
Generated output is committed: __pycache__/.
Add these to .gitignore and `git rm -r --cached` them. Generated files pollute search results, so an agent grepping for a function finds the compiled copy and edits the wrong file.
✓.gitignore hygiene
3/3
.gitignore covers 43 patterns.
✗File sizes fit in context
0/6
18 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
codegraph-kernel/grammars/scala/parser.c — 26186KB
codegraph-kernel/grammars/kotlin/parser.c — 23096KB
codegraph-kernel/grammars/dart/parser.c — 6016KB
✓Repository weight
5/5
About 38.8MB checked out, which is comfortable.
Here is your AGENTS.md
Drafted from what is actually in this repository: the install
command from your lockfile, the commands you already declare, your real directory layout. Anything
marked TODO needs a person. Save it at the root as AGENTS.md.
# AGENTS.md Pre-indexed code knowledge graph, auto syncs on code changes, for Claude Code, Codex, Gemini, Cursor, OpenCode, AntiGravity, Kiro, CoPilot, and Hermes Agent — fewer tokens, fewer tool calls, 100% local ## Setup ``` npm ci ``` ## Commands ``` npm run dev # run locally npm run build # produce a build npm run test # run the test suite, must pass before any commit npm run build:ui npm run build:lib npm run preuninstall npm run copy-assets npm run build:kernel ``` ## Layout - `__tests__/` 681 source files - `src/` 278 source files - `ui/` 91 source files - `scripts/` 70 source files - `codegraph-kernel/` 47 source files - `telemetry-dashboard/` 13 source files ## Conventions - Tests live alongside the code they cover, following `__tests__/adaptive-explore-sizing.test.ts`. - TypeScript runs in strict mode. Type errors are the fastest feedback available, so do not weaken it. - CI defines what passing means. See `.github/workflows/deploy-site.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `codegraph-kernel/grammars/scala/parser.c` is 26186KB. It will not fit comfortably in context, so read it in parts. --- Drafted by agentreadme.com from what is in this repository. Everything marked TODO needs a human. Check it in as AGENTS.md at the root.
Open the raw markdown
or
curl -o AGENTS.md agentreadme.com/draft/colbymchenry/codegraph.md
A draft gets the commands right and stops at the things only a maintainer knows. what AGENTS.md is explains the format itself.
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/colbymchenry/codegraph)Other C repositories, marked
Think this mark is wrong?
Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.