Repo Docs Skills

Repo-Docs: Keep up with the code your agents write. An evidence atlas for agent-built code.

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.

Chinese README | Skill contract | Project homepage | Install

Why now | The loop | Artifacts | Quality bar

Understand the repo before you memorize paths.

---

The Problem

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 reports 932,791 agent-authored pull requests across 116,211 GitHub repositories, while a multi-method census of 180 million repositories 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

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