How it works

Automatically reviewyour PRs with your ownAnthropic API key

Ship faster. Break nothing. A second pair
of eyes on every pull request.

The diffy dashboard: live status, tokens and reviews, and a heatmap of reviews over the last year

From pull request to posted review, diffy does the reading for you.

  1. 01

    A pull request opens

    GitHub tells diffy through a webhook. There is nothing to add to your CI.

    Explore more
  2. 02

    diffy reads the change

    It reads the diff with the files around it and a short brief of the project, so it knows what the change touches.

    Explore more
  3. 03

    Your model reviews it

    The review runs on the model you picked, with your own API key. Your code goes to that provider and nowhere else.

    Explore more
  4. 04

    One review is posted

    Comments on the lines they are about and a single summary, under the heading Summary.

    Explore more

Bring the model you already pay for. Switch whenever you like.

Each organization adds its own API key. Keys are encrypted and stay on your server.

Questions, answered

Where your code goes, what diffy reads, what it costs and how you shape a review.

  • Where does my code go?

    diffy reads the pull request from GitHub on the server you run, and sends the parts it needs to the model you picked, with your own API key. It goes to that provider and nowhere else, and the review is posted back to the pull request.

  • What does diffy read when it reviews?

    The diff, the function or class around each change, and small files in full. Before every review it also reads a few documents from the default branch: the context files you name, rules files such as AGENTS.md, the README and CONTRIBUTING.md, and a short brief of the repository. Lockfiles and generated files are skipped, and the review lists the documents it read.

  • How are my API keys kept?

    A key is encrypted before it is saved, and the secret that unlocks it stays on your server. It is never shown again: the settings show only its last four characters, and an error that could echo a key is cleaned first.

  • What does a review cost?

    You pay your model provider for what the reviews use; diffy adds nothing to that. The cost grows with the size of the change, and the dashboard shows the usage. A setting can send plain patches instead of the code around them, which is cheaper and shallower.

  • Can I configure it myself?

    Yes. A .diffy.yaml file at the root of the repository sets the language of the review (English or Thai), whether it is chill or assertive, instructions for the whole project or for certain paths, more documents to read, and files to ignore. It is read from the default branch, so a pull request cannot change the rules of its own review.

Stop skimming PRs.Start shipping impact.