All Documentation

Everywhere else

Documentation Everywhere else

Review a repository from a link

Paste a GitHub repository link in a new discussion, and the room reads the repository and writes a review of it.

Paste a GitHub repository link into the message box of a new web discussion, and a card appears above the box: Review This Repository. The room reads the repository, checks its own findings with a second seat, and writes the review into the discussion. It is a static review. Nothing is run, built or tested, and nothing is posted to GitHub.

How to use it.

  1. Start a new discussion and paste the repository's address on GitHub (owner/name) into the message box. A link to a folder (ending in /tree/main/src) or to a branch or tag (ending in /tree/v1.2) reviews just that.
  2. Choose what to review for: General review (it works out what kind of repository it is and spends the review where that matters), Security, Code quality or Architecture.
  3. Press Review This Repository. You are taken to the discussion, and the review is written there.
  4. Carry on in the discussion: ask about a finding, or ask a seat to fix one.

Your words stay in the message box, so you can still send them as an ordinary message if you would rather not review the repository.

What the review contains

Findings by severity, each with a file and line, a recommendation and a status (confirmed when the room read the lines, unverified when it inferred it, disputed when a checking seat disagreed); what the repository does well; a table of next actions by priority; a verdict; and a Scope and limits section listing the files it opened and what it did not do.

What it can read

RepositoryHow it is read
PublicWith no sign-in and no install.
PrivateOnly through a LetThemBuild GitHub App installation, yours or your team's, that covers it (Settings → Account → Connected). A repository that is neither public nor covered gets one answer, "not public or not covered", whether or not it exists.

A file whose name says it holds credentials (.env, private keys and the like) is never read, never listed and never quoted. A large repository is read for its code and documentation: files over 300 KB are left out, and checked-in data files (results, transcripts, logs) share a small allowance. When anything was left out, the review says how many in its Scope and limits. An archive over 40 MB packed is refused, with a suggestion to link a folder inside it.

What it costs

It is a discussion on your account like any other, paid from your credit or your own keys, and it counts against your plan's discussions. The room runs on the cheaper model of each seat. It reads with twelve lookups at most, and it stops at one dollar. Most repositories cost a few cents to fifty cents. At most ten repositories a day can be reviewed from one account, and three discussions at once.

Safety

The repository is somebody else's words, so the room is given only tools that read that one repository: no web tools, nothing that writes, nothing that reaches elsewhere. What it reads is material, never instructions: a file that tells the room to do something, including a repository's own CLAUDE.md or AGENTS.md, is ignored.

Pull requests are not reviewed this way. The GitHub App reviews them when they are opened, or when someone comments @letthembuild review.

See Also

Not what you were looking for? The help centre answers one question at a time, and the support page says how to reach a person.