01 / source
Start with the docs you already have
Keep architecture notes, runbooks, product decisions, and agent instructions close to the teams that maintain them. RepoWiki turns those files into a workspace people can actually read.
Docs / product guide
Bring repo docs into one readable workspace.
RepoWiki brings Markdown, MDX, runbooks, and agent instructions from multiple repositories into one private reading and search workspace.
Details
The RepoWiki workflow.
This guide explains the core workflow: connect the right docs, keep the workspace private, make answers searchable, and preserve source details for confidence.
02 / sync
Choose what enters the workspace
Connect the repositories and paths that matter. Each sync keeps repository, branch, path, commit, and hash details attached when readers need to verify a page.
03 / read
Give every team a reader
Browse by workspace, project, and repository, then search across all indexed docs without guessing which repo holds the answer.
04 / safety
Keep sensitive material out
Use private workspaces for team docs and agent context. Keep secrets, credentials, and regulated data out of docs, even when the workspace is private.
workspace snapshot
Details stay close to the content.
RepoWiki is most useful when every page can answer three questions quickly: where it came from, when it changed, and who can read it.
Source
Selected repos · docs/ · main
Content
Markdown and MDX
Details
repo, branch, path, commit
Boundary
private workspace members