Linear Diffs — code review inside Linear
Present a review as four causally connected actions: select a change, compare the diff, leave a comment and submit the review. Make code ownership and comment placement clear.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Linear Diffs — code review inside Linear · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090a0c}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Motion and composition
Local motion · Composition rules
Select a change before entering the diff
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Linear Diffs — code review inside Linear · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090a0c}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="5" data-end="19"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>The changes list establishes the file scope; clicking opens the corresponding code. Keep the filename and selected state visible, and highlight key lines in the diff close-up without scrolling multiple unrelated areas simultaneously.
Place explanations beside the code and comments next to their target lines
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Linear Diffs — code review inside Linear · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090a0c}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="19" data-end="40"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Place the explanatory document beside the code to explain the current change. Align the comment entry point with the relevant code line, and keep that line visible during input; submit the full review after completing the comment.
Red and green carry explicit meanings
Red denotes deletions and green denotes additions, while the rest of the interface uses black, gray and cool purple for hierarchy. Use monospace for code and sans-serif for explanations and buttons; angled views and zooms must not alter the correspondence between files and lines.
Present the product message after submission
The submit button and completed state conclude the review sequence. Once the action is complete, remove the details and give the message and brand their own hold; do not open another file in the ending.
Adapt to manuscript or design reviews too
Retain object selection, before-and-after comparison, anchored comments and explicit submission. When replacing diff content, update filenames, explanations, comments and completion states together; colors must continue to convey consistent comparison meanings.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Adapt to manuscript, design diff or configuration reviews; retain select → compare → comment → submit.
Production constraints
Review list / Code diff / Explanatory document / Comments / Submit button
- Select a change before viewing its diff, anchor the comment to a code line, and explicitly submit the review at the end.
- Preserve the addition and deletion meanings of green and red diff colors; an angled camera must not change which code belongs where.