recall

Reconstructs recent working context from chat transcripts and shared records into a status brief.

3|2|Updated Aug 28, 2026
One-click install
npx skills add https://github.com/adjohn/pstack --skill recall-adjohn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recall
Source: https://github.com/adjohn/pstack/tree/main/skills/recall
Command: npx skills add https://github.com/adjohn/pstack --skill recall-adjohn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you return to a project after days away, you lose track of what you were doing, which PRs shipped, which fixes got reverted, and what users are still reporting. This Skill rebuilds that working context from your Claude Code chat history and the shared engineering record so you can resume work without re-reading everything yourself. ## Core Features & Use Cases - Parallel transcript mining: Fans out subagents over your ~/.claude/projects/ session transcripts to extract goals, decisions, open threads, and artifacts per chat. - Shared-record sweep: Searches source control, issue trackers, chat channels, docs, and error tracking for the history around a named feature or bug, including reverted fixes and recurring user symptoms. - Live-state verification: Checks surfaced PRs, branches, and tickets against git and gh so the brief reflects current truth, not stale history. - Use Case: Before resuming work on a payment retry feature, ask for a recall and receive a capsule with thread statuses like [open PR #412] and [reverted #387], the top recurring problems, and the single best next move. ## Quick Start Ask the assistant to recall your work on a specific feature or catch you up on where you left off this week.

Frequently Asked Questions about recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catch up on what I was working on in Claude Code?▼

Ask to recall your work on a topic or catch you up. The Skill mines your recent session transcripts in parallel, verifies PRs and branches with git and gh, and returns a brief with thread statuses, problems, and the next move.

How does recall search my Claude Code chat history?▼

It spawns parallel subagents over the JSONL transcripts in ~/.claude/projects/, ordered by modification time. Each subagent greps the topic, reads only matching regions, and returns goals, decisions, open threads, and artifacts cited by chat UUID.

Does recall look beyond my own chat transcripts?▼

Yes. When you name a feature, file, or bug, it also sweeps the shared record: source control, issue trackers, chat channels, docs, and error tracking. This surfaces reverted fixes and user-reported symptoms that never appear in your own transcripts.

When should I use recall instead of resuming a specific session?▼

Use recall when you need broad working context across recent chats before acting. If you already know the exact prior chat to continue, that is a session-pickup task instead, and recall explicitly routes away from that case.

Can recall read transcripts from other projects?▼

No. It defaults to the active workspace and never reads another project's transcripts unless you explicitly ask. It also pins a time window, defaulting to the last 7 days, before searching.