What makes a repository illegible
Across hundreds of recorded agent sessions, the failure mode is almost never syntax. Agents stall when a codebase accumulates parallel helpers that do the same job, unindexed files that exceed an agent’s single-read window, or stale .gitignore and prompt rules that point at deleted directories.
| Check | What it catches | Why it matters for agents |
|---|---|---|
token-budget |
Source files and fixtures exceeding o200k_base token thresholds |
Prevents a single file read from evicting architectural context |
dead-context |
Unreferenced modules, orphan templates, and stale ignore entries | Stops agents from editing dead code paths and parallel helpers |
import-cycles |
Circular dependencies and boundary violations across packages | Keeps subsystem dependency graphs shallow and predictable |
doc-drift |
Broken path references and contradictory rules in repo Markdown | Ensures instructions in AGENTS.md and docs match reality |
Correlating static structure with agent transcripts
When paired with Fractal OS, srclint joins static repository checks against actual agent execution logs—highlighting the exact files where agents spend twenty turns reading without making an edit: