Diffs

Review git diffswithout a full checkout

Paste a unified diff, upload a patch, or send git output from CI. CodeCritic analyzes only what changed, which is how experienced reviewers already read pull requests.

unified diffpatch filesline anchorsmulti-fileno repo clone required
How it works

Workflow

How teams wire it

  1. 1

    Produce the diff

    Use git diff, gh pr diff, or CI artifacts that preserve before and after context.

  2. 2

    Submit to CodeCritic

    Web paste, API POST, or GitHub integration depending on where you work.

  3. 3

    Read anchored findings

    Each item references file paths and lines from the diff hunk headers.

  4. 4

    Iterate locally

    Fix, regenerate the diff, and re-run until blocking items clear.

Examples

Integration examples

Minimal unified diff

Reviews anchor findings to these line markers.

diff --git a/lib/billing.rb b/lib/billing.rb
index 3a4b5c6..7d8e9f0 100644
--- a/lib/billing.rb
+++ b/lib/billing.rb
@@ -12,6 +12,7 @@ module Billing
   def charge(user, cents)
+    raise ArgumentError, 'negative amount' if cents.negative?
     Stripe::Charge.create(amount: cents, customer: user.stripe_id)
   end
 end

FAQ

Common questions

Standard unified diff hunk headers with a few lines of context work best. Single-line changes without context may produce weaker anchors.

Related pages

PR automationREST APIOnline paste tool

Start from the diff you already have

Copy git diff output into a new review and compare findings to your last manual pass.

Integrations