About this block

Code Review Thread is the pull request inline discussion pattern: a diff panel for src/lib/retry.ts with old and new line number gutters, a removed row and two added rows tinted from theme tokens, and a comment thread anchored to line 21. Maya Chen asks whether backoffMs caps the delay, Jordan Lee confirms it clamps to a 20 second ceiling and promises a test, and a reply composer sits below as Noah Park. The file header carries added and removed badges, and the thread carries an Unresolved badge with a Resolve conversation action.

Diff rows are two typed arrays, one above the thread and one below, each row tagged context, add, or del to pick its tint and sign. The composer renders as static markup rather than a Radix control so it stays inside the preview root and screenshots correctly. The footer note explains that resolving collapses the thread and that it stays pinned to line 21 as later commits shift the code.

When to use

Reach for this block wherever code changes get discussed on a specific line, wired to your diff endpoint and comment API. Bind Reply to your thread mutation and Resolve conversation to your thread-close call.

A natural flow around it on an Application Pro page:

Before

• Developer tools

After

• Comment sidebar
• Resolved comments list

What you can display

One strong use is the pull request line comment. Other diff anchored threads:

• Config change review. A YAML diff with a thread questioning the new timeout value.
• Migration approval. A schema diff and a thread from a DBA asking about the index rebuild.
• Docs pull request. A prose diff with a thread suggesting a clearer heading for the section.

Tip: keeping the thread attached to the line rather than a file offset is what survives rebases, anchor to the logical line so the conversation follows the code.