inline

Repo wiki and docs drift

An overview, the architecture, a page per module, key flows and a glossary, each naming the commit and files it was written from. On every push only the pages whose files changed are rewritten, and docs drift quotes each stale line with a correction.

1:31 · narrated, with captions · Code reviewRead about Repository wiki

Chapters

What it covers

  • Overview to glossary
  • Rebuilt on push
  • Docs drift
  • Readable over MCP

A wiki for each repository that names the commit and files behind every page, rebuilt on each push, plus docs drift checks on merged pull requests.

Read about Repository wiki

Transcript

The narration as spoken, by chapter. Select a time to play the film from there.

Intro

inline can write a wiki for each of your repositories, and keep it current as the code changes.

Pages

An overview, the architecture, a page per module, key flows, where to change things, and a glossary. Each page names the commit it describes, and the files it was written from, each linked to GitHub at that commit.

Rebuilds

On every push to the default branch, inline rewrites only the pages whose files changed. The rest are left alone.

History

History records every build, even a push where nothing moved, with each page's decision and the files behind it.

Docs drift

Docs drift checks every merged pull request against the docs, and quotes each stale line, word for word, with a correction. Update the docs hands it to a coding session, which edits only the documentation, and opens a pull request.

Agents

Your agents can read it too. inline wiki prints the index in your terminal, and inline ask answers from the pages. Over M C P, each wiki is a resource, not another tool, so it costs an agent nothing until it reads a page. inline. A wiki that keeps up with your code.

Put it on one repository

Connect GitHub or GitLab, enable a repo, and the next pull request opened gets a review.