Review a Pull Request
See what a pull request changed about your design system before it merges.
Primitiv Review leaves a comment on any pull request that touches your design system. A normal code review shows you the lines that changed. This shows you things like: the colour every error message used, the button size three other teams build with.
What it looks like
One comment per pull request. Each row tells you what changed, what it used to be, what it is now, and which file it lives in. The ∅ means it is gone.
Primitiv Review — ⚠️ drift detected
2 changes · 🔴 1 breaking · 🟡 1 review · ⚪ 0 info
| Change | Before → after | Where | |
|---|---|---|---|
| 🔴 | colors/color-destructive removed | #D92D20 → ∅ | tokens.css:23 |
| 🟡 | colors/color-primary value changed | #0055FF → #0044CC | tokens.css:11 |
How serious is it?
| Severity | What it means | |
|---|---|---|
| 🔴 | Breaking | Something people were using is gone. Anything built on it will break. |
| 🟡 | Review | Nothing broke, but a decision changed. A colour, a name, a value. |
| ⚪ | Info | Something was added, or moved somewhere else. |
Primitiv points out what changed. It does not decide whether the change was right, and it never blocks a merge on its own.
Why it existed
If you wrote down why a colour or component exists in your rationale layer, the review brings that reason back with the change:
Design context
colors/color-destructive— Signals destructive and error states.
The reasoning shown is the one that was true before the pull request.
When something can't be checked
If Figma can't be reached, every token in it looks deleted. Primitiv won't call that a change. It says it couldn't check, and leaves it out of the review.
Getting access
Primitiv Review runs as a GitHub app on your repositories. It is available to teams we set up directly. Get in touch and we will walk you through it.