You got a thoughtful review. Someone pointed out a race condition, a clearer naming pattern, or a better way to split the service boundary. You replied "good catch," merged the PR, and moved on.
Two sprints later the same kind of bug shows up. You know you've seen this feedback before. You just cannot find where. Slack search returns forty threads. The PR is buried under merge commits. The lesson never made it into anything you can open when you need it.
That is the code review problem. The feedback was useful. What failed is keeping it after the merge button.
Why review comments evaporate
Code review is high-signal and badly stored. Comments live on a PR that closes. Mentions live in Slack that scrolls. A verbal tip from pairing lives only in your short-term memory until standup ends.
Most people treat review feedback as a one-time fix for that branch. They patch the bug and never extract the pattern. So the next PR with the same shape gets the same comment from the same reviewer, and both of you feel slightly annoyed.
Notes in the PR itself do not help later. When you are designing a new endpoint on a Tuesday, you are not reopening last month's #342 to skim the conversation. You need the idea in a place you actually revisit.
Capture the lesson while the PR is still open
The useful window is short: while the review thread is still warm, before you squash and forget.
When a comment teaches you something reusable, save it as its own artifact. That can be the PR URL, a screenshot of the comment, or a short note you write in your own words. One sentence like "prefer context deadlines over sleeping in retries" beats a vague "review was good."
I use Recl for this. Share-sheet save from the GitHub mobile app, Chrome right-click on the PR page, or Ctrl/Cmd+Shift+S drops the link into a library. A photo of a whiteboard sketch from a design review works the same way. The point is getting the lesson out of the ephemeral thread before it closes.
Do not try to archive every nitpick about commas. Keep the patterns you would teach a teammate next month.
Turn the comment into takeaways you can reuse
A raw PR URL is still hard to search under pressure. What you want is a short map: what broke, what the reviewer suggested, and the rule you will apply next time.
Write that rule in your voice. "If a goroutine outlives the request, cancel with context" is better than pasting three paragraphs of review prose. Add a "Your note" card if your tool supports it. Folders or auto topics help when reviews span auth, caching, SQL, and frontend state in the same week.
In Recl the save gets a short summary first, then a fuller one with key takeaways. You can ask your library later, "what was the retry pattern from that payments review?" and get an answer from your own saves with sources. Browsing library.recl.app shows how a clean takeaway card reads; your private saves are the ones that matter for your team's quirks.
Delete vibes-only comments. If the only note was "LGTM," it does not need a forever seat.
Schedule light recall so the pattern sticks
Saving is not remembering. You need a reason to see that lesson again before the next similar PR lands.
A simple loop works: a nudge a few days later that asks whether you still remember the rule, then a short weekly quiz on what you saved. Answer in one line. If you blank, open the takeaway card, not the whole PR thread.
That is the Recall side of Recl. The nudges stay light. You are keeping a handful of engineering patterns warm enough that they show up when you open a new branch, not building a second Anki deck you will abandon.
Ask when the next PR looks familiar
The real test is Thursday afternoon when you are about to write another retry loop, and something in the back of your head says "we got burned by this."
Instead of grepping Slack for "retry" and hoping, ask your library. Pull the takeaway. Apply it before the reviewer has to type the same comment again. That is when capture after review pays rent.
Capture while the thread is open. Compress the same day. Light recall through the week. Ask when the next design looks familiar.
A week that fits real review load
Keep the habit small enough that it survives a week of three big PRs and a production fire.
After a useful review comment: save the PR or your one-sentence rule within ten minutes of merging. Skim the short summary. Folder it under the topic if it is obvious (auth, data, concurrency).
Later that week: answer one recall prompt without opening GitHub. If you fail, reread your sentence.
Sunday: glance at the weekly quiz for what you saved. Drop anything you cannot explain. Keep the rest.
Chrome users can save the PR page with a shortcut or right-click while the review is still on screen. None of that replaces the ten-minute rule. Tools only help if you capture while the feedback is still sharp.
What you are actually building
Skip the graveyard of closed PRs and unread Slack pins. Build a short shelf of review lessons you can apply on the next branch.
The merge was never the asset. The reusable rule was. Capture it, summarize it, revisit it, and ask for it when the next PR rhymes with the last one. If you want that loop in one place, from share-sheet save through summary and recall nudges to asking your library, Recl is built for it. Save what matters. Recall it forever.
Asutosh builds Recl, an app for saving what you learn and remembering it later. Writing about learning in public at @richspartan430.
