Behavior first
See added, updated, and removed capabilities through before and after scenarios.
Understand the change before you say yes.
AI-assisted GitHub pull request reviews, explained through behavior and evidence.
Sign in to browse your repositories and review pull requests.
Continue with GitHubAccess is limited to repositories you can read and have connected to Diff it.
See added, updated, and removed capabilities through before and after scenarios.
Trace each explanation to the source at the commits being reviewed.
Inspect UI, security, architecture, and operational checks with their actual status.
THE REVIEW BEHIND THE DIFF
Diff it is an AI-assisted GitHub pull request review workspace for developers and reviewers. It organizes code changes into added, updated, and removed capabilities, with before and after scenarios, source evidence, and verification status.
Use it to understand a pull request before approving it, investigate behavior changes, or return to the evidence behind a previous review.
FROM CODE TO A REVIEW DECISION
Sign in with GitHub and select a connected repository you can read. Open a pull request to analyze the change at its base and head commits.
Read what changes for users and systems, compare before and after scenarios, and follow source citations. Inspect proposed checks and any available verification results across UI, security, architecture, and operations.
Use the analysis to guide your own review. A proposed check is not a passing test. Review comments are posted to GitHub only when you submit them, and Diff it does not automatically merge pull requests.
BEFORE YOU REVIEW
Diff it groups a code diff by capability: what is added, updated, or removed. Each explanation connects before and after scenarios with source evidence and check status, helping reviewers understand a change beyond individual lines of code.
Yes, when you can read the repository and it is connected through the GitHub App installation. Signing in does not grant access to every repository: Diff it checks both your permissions and the installation's repository access.
No. Source citations show the code supporting an explanation; they do not prove runtime behavior. Proposed checks are separate from observed verification results. Review the actual status and run the checks your change requires.
Yes. Saved analyses are restored when you reopen a review. Access still requires GitHub sign-in and permission to read the repository.
No. AI explanations can be incomplete or incorrect, and source context may be missing. Inspect the cited code, verify the behavior, and make your own review decision. Diff it does not guarantee that a change is safe to merge or that every bug is found.