Choose a pull request, then select a component to see its evidence and next step.
From pull request to review
How it works
Connect a GitHub repository.
Give NodeDots the repository context for your review.
Open a pull request as usual.
Keep working in GitHub with your team and existing tools.
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.