recall

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When resuming work after days away, you lose track of what you decided, which PRs shipped, and what problems remain. This Skill rebuilds your recent working context from your own Claude Code chat history and the shared engineering record, then hands back a tight current-state brief. ## Core Features & Use Cases - Chat history mining: Spawns parallel read-only subagents that grep and read your Claude Code session transcripts, returning decisions, open threads, and artifacts per chat. - Shared record sweep: Searches source control, issue trackers, chat channels, docs, and error tracking for user-reported symptoms, shipped-and-reverted fixes, and open incidents related to the topic. - Live state verification: Cross-checks surfaced PRs, branches, and tickets with git and gh before writing the brief. - Use Case: You return from a week off and ask "catch me up on the auth migration". The Skill mines your recent sessions, sweeps the shared record for related bugs and reverts, verifies branch and PR status, and returns a capsule with tagged thread statuses and the single best next move. ## Quick Start Ask the assistant to recall your work on a specific feature or subsystem and catch you up on where things stand.

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 my recent work in Claude Code?▼

Invoke the recall skill with a topic, such as "recall my work on the auth migration". It mines your recent session transcripts, sweeps the shared record, verifies live git and PR state, and returns a brief with thread statuses and a next move.

Where does Claude Code store session transcripts?▼

Transcripts live at ~/.claude/projects/<slug>/<session-id>.jsonl, where the slug is the working directory with non-alphanumeric characters replaced by dashes. Each line is a JSON record carrying message content, cwd, and timestamp.

Does recall search sources outside my chat history?▼

Yes. When the topic names a feature, file, or bug, it sweeps the shared record through the why skill's investigators: source control, issue trackers, chat channels, docs, and error tracking. Pure activity recall with no named target skips this step.

Can recall read transcripts from other projects?▼

No. Scope is locked to the active project's slug plus its worktree slugs by default, and the skill never reads another project's transcripts unless explicitly asked. It also skips the current session and subagent noise directories.

When should I use session-pickup instead of recall?▼

Use poteto-mode's session-pickup playbook when you want to resume one specific prior chat. Recall is for rebuilding working context across many recent chats before starting or resuming work on a topic.