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.
An impact report for developers and teams, right on the pull request.
Early access. One email when it opens.
What you're signing up for
- A review of what a pull request breaks, forgets, or leaves untested.
- Early access starting with GitHub pull requests.
- One email when early access opens.
See it catch something
In this example, a developer replaces Firebase Auth with Clerk. NodeDots finds the one place that still uses the old ID.
- Ingest: done
- Parse: done
- Graph: done
- Evaluate: done
- Report: done
Illustrative exampleFirebase → Clerk
One change. Five connected components.Analyzed in 6.6s
Conflicting
New identity. Old billing assumption.
The PR switches to Clerk. Stripe customer lookup still uses a Firebase UID, so existing customers may lose their billing link.
api/billing/customers.ts:42where: { firebase_uid: user.id }3 confirmed, 1 conflicting, 1 missing
Before merging- Map existing Stripe customers to Clerk IDs.
- Test signed-out redirects before merging.
report 3 confirmed, 1 conflicting, 1 missing
- Confirmedchecks out
- Missingexpected but absent
- Conflictingtwo parts disagree
- Uncertainnot enough evidence
- Action requiredneeds your decision