Code review
Review AI changes
When an AI coding tool changes how your product works, it proposes the change to your diagrams. People review it as a visual diff, comment on the exact box, and merge.
The loop
- Link the codebase. Ask your tool to connect the repo to its diagrams. It writes
.nodeslate/config.json; commit it so every developer's tool uses the same diagrams. - Code changes the design. When your tool adds a service, a table or a step, it reads the diagram and calls
propose_changewith what changed and why, mentioning the pull request. - People review. Reviewers get an email and open the change request: a diff with new boxes in green, changed ones in orange and removed ones struck through, for flows, architecture and databases alike.
- Ask about the exact box. A reviewer comments on the step or table that looks wrong. The tool reads the thread, answers it, fixes the code and the diagram with
update_change_request, and replies with what it changed. - Approve and merge. Only people approve and merge. The team's diagram now shows how the system really works.
Protected main
A workspace can protect main, so changes need approval before they land. Owners and admins choose how many approvals are needed in the workspace's settings. AI tools can't edit a protected main: add_to_diagram and propose_change open change requests instead.
Conflicts
If main changed while a change request was open, Nodeslate merges both sides box by box. When both sides changed the same thing, removed something the other changed, or added something with the same name, the change request shows each conflict side by side, and a person picks what to keep. Nothing is overwritten silently.
Prompts that work
- “After this change, update the Nodeslate diagrams it affects and ask Priya to review.”
- “Read the review comments on change request 3 and address them.”
- “Add the new refunds table to the database diagram as a change request.”
Stuck, or missing something? Contact us.