Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Living project docs for coding agents: keep guides, progress logs, change maps, and handoff context updated as your repo evolves.
| Date | Stars |
|---|---|
| 2026-07-24 | 411 |
| 2026-07-25 | 417 |
| 2026-07-28 | 419 |
| 2026-07-30 | 419 |
| 2026-07-31 | 430 |
| 2026-08-06 | 430 |
Today
— stars today
This week
+11 stars this week
This month
— stars this month
Momentum
19.4
growth rate 2.63%/day
<div align="center">
<img src="site/assets/logo.png" width="86" alt="Repo-Docs logo" />
<h1>Repo-Docs: Keep up with the code your agents write.</h1>
<p><strong>An evidence atlas for agent-built code.</strong></p>
<p>
Vibe coding makes code move faster than memory. Repo-Docs turns each real
run into walkthroughs, concepts, references, and sync rules that live beside
the source.
</p>
<p>
<a href="http://xhslink.com/o/9M27ebWDaD3">
<img alt="RedNote(小红书)" src="https://img.shields.io/badge/RedNote(%E5%B0%8F%E7%BA%A2%E4%B9%A6)-Post-ff2442?style=for-the-badge&labelColor=555" />
</a>
<a href="https://yurunchen.github.io/repo-docs-skills/">
<img alt="Project homepage" src="https://img.shields.io/badge/Project%20Page-Online-27a36f?style=for-the-badge&labelColor=555" />
</a>
</p>
</div>
<p align="center">
<a href="README_CN.md">Chinese README</a> |
<a href="skills/repo-docs/SKILL.md">Skill contract</a> |
<a href="https://yurunchen.github.io/repo-docs-skills/">Project homepage</a> |
<a href="#install-in-30-seconds">Install</a>
</p>
<p align="center">
<a href="#why-this-exists-now"><strong>Why now</strong></a> |
<a href="#the-repo-docs-loop"><strong>The loop</strong></a> |
<a href="#what-it-builds"><strong>Artifacts</strong></a> |
<a href="#quality-bar"><strong>Quality bar</strong></a>
</p>
<p align="center">
<img
src="site/assets/main.png"
alt="Repo-Docs main preview"
width="900"
/>
</p>
<p align="center">
<em>Understand the repo before you memorize paths.</em>
</p>
---
## The Problem
<table>
<tr>
<td width="50%" valign="top">
<h3>Agent-built repos often feel like this</h3>
<ul>
<li>Code changed quickly, but the reason stayed in chat.</li>
<li>Files exist, yet no one can explain the real behavior path.</li>
<li>README, source, tests, and agent memory drift apart.</li>
<li>The next agent starts by rediscovering the same context.</li>
</ul>
</td>
<td width="50%" valign="top">
<h3>Repo-Docs leaves this behind</h3>
<ul>
<li>A walkthrough of one real run from entry to output.</li>
<li>Concept pages for the few ideas that actually matter.</li>
<li>Evidence pages for source proof and quality review.</li>
<li>A sync rule that keeps future answers tied to current source.</li>
</ul>
</td>
</tr>
</table>
Repo-Docs is not a file-tree tour, a generated API dump, or a chat transcript.
It is a small project guide that tells a reader what the repo does, how the
behavior moves, where the proof lives, and how to keep that understanding fresh.
## Why This Exists Now
AI coding is no longer a niche workflow. Two 2026 open-source studies make the
scale visible: [AIDev](https://arxiv.org/abs/2602.09185) reports 932,791
agent-authored pull requests across 116,211 GitHub repositories, while a
[multi-method census of 180 million repositories](https://arxiv.org/abs/2606.24429)
shows that many agent traces are missed by single-signal detection.
That growth creates a new maintenance problem: the code may be real, but the
project understanding is often temporary. Repo-Docs gives coding agents a
repeatable way to preserve the reasoning layer inside the repository itself.
## The Repo-Docs Loop
```mermaid
flowchart LR
A["User asks or agent changes repo"] --> B["Understanding sync check"]
B --> C["Update README and walkthrough"]
B --> D["Update change-log"]
B --> E["Patch modules / glossary / references"]
B --> F["Update AGENTS.md / CLAUDE.md"]
C --> G["User can read the current project"]
D --> G
E --> G
F --> G
```
The loop is intentionally conservative. A good update touches the page that
would otherwise mislead the next reader, not every page that could be polished.
## What It Builds
| Artifact | Job |
| --- | --- |
| `repo-docs/README.md` | Orient the reader and point to the first useful path. |
| `walkthroughs/one-real-rExcerpt of 8,965 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:0a13f727cbded493, topic:vibe-coding