Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>PRoctologNew to Visual Studio Code? Get it now.
PRoctolog

PRoctolog

Lemuel Cushing

|
3 installs
| (0) | Free
Read, comment on and tick off a pull request's code from the PRoctolog review desk. Your comments stay on your Mac, never on GitHub.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

PRoctolog code

The code half of PRoctolog, a review desk for stacks of pull requests an agent wrote. The desk runs on your Mac and walks you through each pull request's description. This extension is where you read its code.

On its own it does nothing at all, which is a kind of discretion. You need the desk first.

What you get

Press d on a pull request's page on the desk, and VS Code opens:

  • every file the pull request changes, in one diff, both sides read straight from git;
  • a PRoctolog view in the side bar listing the files, with a box to tick once you've read each;
  • comments in the gutter, on either side of the diff or on a whole file, with replies. A thread can be resolved, reopened or withdrawn.

Your comments and ticks stay on your Mac. GitHub never hears of them, which is the point, and why it works on pull requests nobody has opened yet. The desk picks them up and hands them to your agent with the rest of your review.

When the pull request moves on, a comment follows its lines. If they're gone, it stays where you wrote it, marked stale.

Install

proctolog setup installs it. By hand:

code --install-extension LemuelCushing.proctolog

Weak spots

  • A window holds one pull request.
  • A comment can't be edited once written.
  • A comment on a file the pull request no longer touches is kept but not shown.

How it talks to the desk

Through the pull request's folder in the desk's marks (its store on your Mac):

  • review.json: what is compared, written by the desk.
  • comments.json: your threads, each with the base and head it was written on.
  • viewed.json: your ticks, by path and blob.

The desk reads only the last two, the extension only the first.

Working on it

npm install
npm test           # opens a toy pull request in a VS Code of its own and checks what it drew

The test needs VS Code installed (or VSCODE=/path/to/Code, or none: it downloads one) and leaves its pictures in .check/. It never touches your own VS Code profile. node test/trial.js LINK opens a real desk's link the same way.

Releases: npm version patch && git push --follow-tags, and the Publish workflow takes it to the Marketplace (it wants a VSCE_PAT secret).

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft