# Diff it

> 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.

Slogan: "Can you merge my PR?"

**Connect a repository and open a pull request.** 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.

**Understand the behavior and inspect the evidence.** 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.

**Make the review decision.** 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.

**What does Diff it add to a pull request 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.

**Can I review private GitHub repositories?**

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.

**Does an explanation mean the change has been tested?**

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.

**Can I return to a saved analysis?**

Yes. Saved analyses are restored when you reopen a review. Access still requires GitHub sign-in and permission to read the repository.

**Can AI review replace human review?**

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.

This guide describes the public product only. Repository contents, reviews, saved runs, and account data require authorization and are not included here.

## Public product information

- [Product overview](https://diff-it.dev/#overview): What Diff it does and who it is for.
- [How it works](https://diff-it.dev/#how-it-works): Connect a repository, inspect the analysis, and make a review decision.
- [Frequently asked questions](https://diff-it.dev/#faq): Repository access, evidence, saved analyses, and AI limitations.
- [Blog](https://diff-it.dev/blog): Practical guides to reviewing changes and verifying behavior.
- [What does this PR actually change?](https://diff-it.dev/blog/what-does-this-pr-actually-change): We ran a public gRPC pull request through Diff it, then checked its behavior explanation against the pinned implementation and regression test.
- [How to review AI-generated pull requests](https://diff-it.dev/blog/how-to-review-ai-generated-pull-requests): A practical review checklist for AI-generated code: recover the intended behavior, inspect boundaries, trace evidence, and choose checks that can disprove the explanation.
- [How to verify behavior changes when CI is green](https://diff-it.dev/blog/verify-behavior-when-ci-is-green): Turn a pull request’s behavior claims into targeted checks for success, rejection, and failure paths, even when the existing CI suite passes.