Give private code a proper review surface.

RepoView turns a private repository into a scoped, read-only link that feels familiar to the person reviewing it — and gives you a useful signal when they engage.

  • Read-only by design
  • No viewer account
  • Expiry and revocation are yours
What the recipient sees scoped share

A familiar repository review, without repository access.

Recipients open the link and start reading. They can move through the files and rendered content you chose to share, without creating an account or seeing an edit surface.

  • Open and read immediatelyNo viewer sign-in or setup for the person reviewing your work.
  • Keep technical context intactMarkdown, source, images, and diagrams stay in one repository-shaped view.
  • Stay read-onlyA share provides a review surface, not repository credentials.
Recipient pathread only
tekkscope / repoviewPrivate repository
README.mdRendered first, with the authorized tree beside it
mainThe ref you selected

The repository remains private on GitHub.

You decide what leaves your workspace.

Choose the repository and ref, keep the share read-only, and decide how long the link should work before you send it.

Read-only accessRecipients can review the files you authorize, not edit them.
Owner-controlled GitHub accessRepoView retrieves repository content server-side.
Expiry or revocation when you need itEnd access without changing the repository itself.
No viewer account requiredThe link is the entry point for the recipient.

Private code deserves a focused review.

Create a workspace and share your first repository when you are ready.