# Recall

Reconstruct your recent working context from your own chat history, live state, and the...

- Repository: https://github.com/michael-denyer/pstack-claude (3725 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add michael-denyer/pstack-claude --skill recall -g -a claude-code -y`
Codex: `npx skills add michael-denyer/pstack-claude --skill recall -g -a codex -y`
Cursor: `npx skills add michael-denyer/pstack-claude --skill recall -g -a cursor -y`
Gemini CLI: `npx skills add michael-denyer/pstack-claude --skill recall -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add michael-denyer/pstack-claude`

## Description

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work, and before telling the user that something was never recorded.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Recall

On GitHub Copilot, read the [platform mapping](../poteto-mode/references/copilot-tools.md), including its per-skill notes, before following this skill.

On Muse, read the [platform mapping](../poteto-mode/references/muse-tools.md), including its per-skill notes, before following this skill.

**Before you start or resume work, you rebuild the user's recent working context and hand back a tight capsule of where things stand now and what to do next.**

Keep it tight and on-topic. Read only what the in-scope threads need, then stop.

Your context lives in two records. Your own chat history holds what you did and decided. The shared record holds everything that happened around the same code under other names: the symptoms users keep reporting, the fixes that shipped and got reverted, the errors still firing in prod. That second record is what the **why** skill searches, across source control, the issue tracker, chat and issue channels, long-form docs, and error tracking. A feature with a long bug tail keeps most of its story there, so don't reconstruct it from your transcripts alone.

Transcripts live at `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/projects/<encoded-cwd>/<uuid>.jsonl`. Every line is one chat message. Run `node <plugin>/skills/reflect/scripts/claude-project-dir.mjs` to print this session's directory rather than building `<encoded-cwd>` by hand. Claude Code turns each character other than an ASCII letter or digit into "-" (so `/Users/you/my_app.web` becomes `-Users-you-my-app-web`), shortens a name past 200 characters with a hash, and takes `CLAUDE_CODE_PROJECT_DIR_NAME` in its place when that is set with `CLAUDE_CONFIG_DIR`.

The rest: https://github.com/michael-denyer/pstack-claude/blob/HEAD/plugins/pstack/skills/recall/SKILL.md