NODEDOTS CODE / PUBLIC REPOSITORY BETA
From your first PR
to a clearer shipping decision.
Practical guides for the product you can use today. Connect GitHub, follow the impact, and give your team the evidence to act.
Check before you push
Run NodeDots locally on working changes, staged files, or two commits. Local advisory analysis for Node.js 22+.
Read guide →02 / Start hereYour first pull request review
Connect GitHub, choose a public repository, and follow the impact of a change.
Read guide →03 / ReviewRead the connected review
Understand the impact map, source evidence, finding states, and saved decisions.
Read guide →04 / ShipPrepare a change to ship
Set repository expectations, add intent, inspect CI, and record release preparation.
Read guide →05 / CollaborateHand off a review
Export the context and grant individual teammates access without making reports public.
Read guide →06 / AutomateReview new commits automatically
Enable advisory GitHub reviews and understand delivery evidence.
Read guide →07 / UnderstandData, permissions, and limitations
Know what NodeDots reads, stores, and leaves unknown.
Read guide →08 / HelpTroubleshoot the workflow
Resolve sign-in, repository visibility, interrupted reviews, and missing CI signals.
Read guide →Current behavior, clear limitations. Reviews are advisory; your tests and human review remain essential.