If you work on more than one thing at a time with Claude Code, you know the problem. You’ve got a worktree for one feature, a terminal for a bug fix, another tab for a PR that’s waiting on review. Each session has built up real context — what was tried, what failed, why a decision was made — and none of that is written down anywhere. It only exists in that one running session.

Claude Code already lets you name a session and resume it later, but in practice that’s tedious. You have to remember the name, remember which terminal, remember which of the five things you were juggling that session belongs to. When you’re deep in several worktrees at once, it’s easy to just lose track.

What I actually wanted was simpler: work on a PR, step away from it, and free up the terminal for something else — without losing everything that session knew.

So I built the pr-memory skill.

What it is

pr-memory keys session memory off the thing you actually care about: the pull request.

• pr-memory save — snapshots the current session as a handoff-style document: the worktree, the branch in every repo you touched, and every related PR across repos.
• pr-memory load <pr> — finds that document by any of those PR numbers and re-hydrates the session from it.
• pr-memory list — see everything you’ve got saved.
• pr-memory gc — prune memories whose PRs have all merged (this also runs automatically in the background).

Say you’re working on myrepo#5. You need the terminal for something more urgent, but you’re not done with #5 yet. Instead of leaving the session running or trying to remember a session name, you just say:

“Save this session”

and pr-memory writes a handoff doc — what was built, current state, open items, key learnings — indexed by #5. The terminal is now free.

Later, review feedback comes in, or you just want to pick it back up:

“Load pr-memory for #5”

and the session comes back: same context, same open items, with an offer to check out the saved branch if you’re not already on it.

It started as a personal skill tied to one multi-repo workspace I use at work, but I generalized it to work standalone with zero config in a plain single-repo checkout, while still scaling up to a multi-repo workspace if you have one.

Final Words

It’s a small thing, but it’s already changed how I juggle multiple PRs — I stop hoarding terminal tabs “just in case” and just trust that save / load will bring the context back when I need it.

It’s part of the hardkoded-skills plugin, open source as always. Give it a try and let me know what breaks.

Don’t stop coding!