recall

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you return to a project after days away, you lose track of what you decided, which branches are in flight, and what users are still reporting. This Skill rebuilds that working context by mining your own chat history and the shared project record, then hands back a tight current-state brief so you can resume work immediately. ## Core Features & Use Cases - Parallel transcript mining: Fans out subagents across your recent chat history to extract goals, decisions, open threads, and artifacts, each cited by chat UUID. - Shared record sweep: Searches source control, issue trackers, chat channels, docs, and error tracking for the history of a named feature or bug, including fixes that shipped and were reverted. - 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 to be caught up and receive a capsule with tagged thread statuses like [open PR #42], the recurring problems users still report, and the single most useful next action. ## Quick Start Ask the assistant to recall your work on a specific feature or catch you up on what you have been working on 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 a project?▼

Ask to recall your work on a topic or to be caught up. The Skill mines your recent chat transcripts in parallel, sweeps the shared project record, verifies branches and PRs against live git state, and returns a brief with tagged thread statuses and a next move.

How does chat history search work across many sessions?▼

Parallel subagents each take a slice of the transcript corpus, order candidates by modification time, grep for the topic, and read only matching regions. Each returns a structured summary citing chat UUIDs, so the main thread keeps only the findings.

Can it recall work on a specific feature or bug?▼

Yes. When you name a feature, file, or bug, it also sweeps the shared record across source control, issue trackers, chat channels, docs, and error tracking to surface shipped-and-reverted fixes and symptoms users still report.

Does it read transcripts from other projects?▼

No. Scope is locked before searching and defaults to the active workspace. It never reads another project's transcripts unless you explicitly ask, and the time window defaults to the last seven days.

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

Use session pickup when you want to resume one specific prior chat. Recall is for rebuilding working context across many recent chats and the shared record before starting or resuming broader work.