Get a first-pass PR review before you open the tab

Email Carly the PR link and she'll do the first-pass review — correctness issues flagged, style nits inline, a summary comment to anchor the discussion — dropped straight into GitHub.

GitHub

What Carly does

1. 01 Fetch the PR — diff, files changed, existing comments
2. 02 Identify correctness issues — null checks, race conditions, edge cases
3. 03 Flag missing tests on critical-path changes
4. 04 Post inline comments for each concern
5. 05 Post a summary comment — verdict, blockers, nits

First-pass reviews in minutes, not days

Authors get specific, inline feedback before they've lost context. The human review focuses on judgment calls — not on counting missing semicolons.

Email this to Carly to kick it off.

Hey Carly,

Can you do a first-pass review on this PR? [paste the GitHub PR link]

Pull the diff, the files changed, and any existing comments so you have context. Then look for correctness issues — null checks, race conditions, edge cases — and flag missing tests on anything that's on a critical path.

Post inline comments for each concern, and finish with a summary comment that calls out the verdict, any blockers, and the nits. Run the inline comments by me before they post so I can spot-check them.

Thanks!

More recipes for engineering teams

Triage Sentry into Linear backlog

Cluster Sentry issues by root cause, match against Linear, and file the rest with stack + occurrence counts.

Read →

Respond to an on-call page

Ack PagerDuty, pull the Datadog window, correlate deploys, start a war-room — so you land in the fix with context.

Read →

Sprint closeout notes

Linear + GitHub stitched into a Notion closeout — what shipped, what carried, wins worth calling out.

Read →