That covers it. Ask a question, or start a new review.
Sign in
or
Your sign-in link is ready.
or
Your sign-in link is ready.
Not signed in to Claude: the reviewer cannot run yet.
Either way, the code is read with your own SSH key: add its public half to the repository's deploy keys (read-only is enough) or to your GitHub account.
No reviews yet.
This review's session has ended: its code was removed from the server.
Copying the code from GitHub…
That covers it. Ask a question, or start a new review.
The steps and answers are removed. Your code is not touched.
On this local instance the reviewer can run on your own Claude subscription instead of the server's API key. In a terminal on this machine run:
claude setup-token
sign in with your Claude account, and paste the token it prints (it starts with
sk-ant-oat). The app checks it with one short question, then keeps it encrypted.
Only its first and last characters are ever shown again.
Reviewgentic reads repositories with this key. Add it to a repository's deploy keys (Settings → Deploy keys, read-only) or to your GitHub account (Settings → SSH keys).
Copied.
The old public key stops working wherever you added it.
No passkey yet: you sign in by email link.
Who may sign in. No invitation is sent: tell the person to ask for a sign-in link. Admins manage people; nobody sees anyone else's reviews.
Reviewgentic walks you through a Python repository the way a patient reviewer would: one small piece of code at a time, in the order it runs, read aloud if you like. You steer: go deeper, skip, back out, or stop and ask.
The app reads repositories with an SSH key made for you alone; nobody else's reviews use it. Open Your account (the person icon), copy the public key, and add it on GitHub: to your account (Settings → SSH and GPG keys → New SSH key) to reach every repository you can read, or to one repository only (its Settings → Deploy keys, read-only is enough). Make a new key replaces it; the old one then stops working on GitHub.
On the home page, paste the repository's address from GitHub (the browser's address or the SSH one both work), or click one you reviewed before. List its branches and pick one. You may choose a file to begin with; otherwise the reviewer finds the entry point. Then say what you want explained, in your own words, or with one of the suggestions, and start. The code is copied for an hour, which you can extend.
Each step shows a few lines and says what they do. With reading aloud on (the speaker icon), the lines are lit as they are read, and the walk goes on by itself when the next step is obvious; pause or stop the reading at any moment. When a call is worth a look, the step offers to step into it, skip it, or take another file. Ask a question, typed or out loud: the answer stays on the code it is about, and the walk carries on from where it was.
Hold Ctrl (Cmd on a Mac) and click a name to open the place it is declared, in whichever file. The arrows beside the file name go back and forward. The folder icon opens any file of the review; Walk through it asks the reviewer to explain that file next, and Back to the step returns to where the walk was. The progress list keeps every step: open one again, or carry on from it.