For GitHub pull requests

Catch What Your Pull Request Missed.

Follow your pull request into connected code, configuration, and tests. Catch missing work and conflicting assumptions before you merge.

Sign in with GitHub to review your first pull request.

The problem

The button works. The cleanup doesn't.

An AI agent adds account deletion. The button works. The database row is gone.

But the Stripe customer, the uploaded files, and active sessions are all still there.

Nothing failed. Something was forgotten.

NodeDots looks for what a change forgot.

See it catch something

Illustrative example

In this example, a developer replaces Firebase Auth with Clerk. NodeDots finds the one place that still uses the old ID.

Change reviewIllustrative example · GitHub pull requests
  1. Ingest: done
  2. Parse: done
  3. Graph: done
  4. Evaluate: done
  5. Report: done
Analyzed in 6.6s
Replace Firebase Auth with ClerkSelect a component

Login: Confirmed. Sessions: Confirmed. User identity: Confirmed. Billing: Conflicting. Tests: Missing

One pull request. The connected repo.

PR #184 opened: Replace Firebase Auth with Clerk
ingest diff fetched · 14 files changed
parse indexing imports, exports, and symbols
parse middleware.ts · 3 imports, 2 exports
parse lib/auth/user.ts · 4 imports, 2 exports
parse api/billing/customers.ts · 5 imports, 2 exports
parse tests/auth/redirect.test.ts · 6 imports, 2 exports
graph traversing component relationships
graph connection 1 established
graph connection 2 established
graph connection 3 established
evaluate Login
graph connection 4 established
graph connection 5 established
evaluate checking evidence against the change
Login · confirmed
evaluate Sessions
Sessions · confirmed
evaluate User identity
User identity · confirmed
evaluate Billing
Billing · conflicting
evaluate Tests
Tests · missing
report 3 confirmed, 1 conflicting, 1 missing
14 changed files
  • app/login/page.tsx
  • middleware.ts
  • lib/auth/user.ts
  • api/billing/customers.ts
  • tests/auth/redirect.test.ts
  • app/layout.tsx
  • lib/auth/session.ts
  • db/schema/users.ts
  • app/signup/page.tsx
  • lib/auth/provider.ts
  • package.json
  • package-lock.json
  • .env.example
  • README.md

report 3 confirmed, 1 conflicting, 1 missing

  • Confirmedchecks out
  • Missingexpected but absent
  • Conflictingtwo parts disagree
  • Uncertainnot enough evidence
  • Action requiredneeds your decision

Choose a pull request, then select a component to see its evidence and next step.

From pull request to review

How it works

  1. Connect a GitHub repository.

    Give NodeDots the repository context for your review.

  2. Open a pull request as usual.

    Keep working in GitHub with your team and existing tools.

  3. Get an impact report.

    A comment on the pull request lists what it affects, what's missing, what conflicts, and a checklist to review before merging.

A “dot” is a piece of your system: a file, route, table, test, or setting.

This is the planned early-access workflow. The example shows the intended output.

Pull request #184 · Firebase Auth → ClerkIllustrative example

NodeDots Impact Report

Comment on the pull request

  • 3 confirmed
  • 1 conflicting
  • 1 missing

Billing still expects the old ID

api/billing/customers.ts:42

Stripe customer lookup uses a Firebase UID. The new login supplies a Clerk ID.

Signed-out redirect test is missing

tests/auth/redirect.test.ts:11

The tests cover signed-in users, but not a signed-out visitor requesting a protected route.

Before merging

  • Map existing Stripe customers to Clerk IDs.
  • Add a test for signed-out redirects.

Who it's for

Developers and small teams who ship with AI coding agents or move fast. Anyone who has been surprised by a side effect after merging.

What it isn't

A code generator or a replacement for tests, linters, or code review.

It checks the work around the change, so your team and your tools can trust the result.

A few useful answers

FAQ

What does NodeDots do?

NodeDots checks a pull request against the rest of your codebase. It reports affected code, missing work, conflicts, and tests to review before you merge.

Does it replace code review, tests, or my linter?

No. It complements them by checking the work around a change, including API assumptions, database migrations, and missing tests.

Which languages and Git hosts?

The first version starts with GitHub pull requests. Supported languages and frameworks: To be announced.

Does it change or run my code?

Code execution and repository permission details: To be announced before early access. The planned workflow is a review report for you to act on.

How is my code handled?

Code processing, storage, retention, providers, and security policy: To be announced before you connect a repository. This waitlist does not connect to or read your code.

When does it launch and what does it cost?

Launch date and pricing: To be announced. The waitlist gets first access; we will send one email when early access opens.

Know what your next change touches.

Explore the review. Follow the evidence. Find the next step.