skills.rest
edivad1999
edivad1999COMMUNITY
Explore all skills by this author →
GitHub

recall

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

1|Updated Aug 26, 2026
Search Tags:#recall#chat history#transcripts#Cursor#session resume#work summary#context recovery
One-click install
npx skills add https://github.com/edivad1999/stuc-stack --skill recall-edivad1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recall
Source: https://github.com/edivad1999/stuc-stack/tree/main/skills/recall
Command: npx skills add https://github.com/edivad1999/stuc-stack --skill recall-edivad1999

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 chat history and the shared engineering record, then hands back a tight current-state brief. ## Core Features & Use Cases - Parallel transcript mining: Fans out subagents across your Cursor chat history to extract topics, 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 and reverted fixes tied to a named feature or bug. - 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 payments refactor". The Skill mines your recent chats, sweeps the shared record for incidents and reverted fixes, 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 to 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 my recent work across multiple chats?▼

Ask to recall your work on a topic or time window. The Skill spawns parallel subagents that grep and read matching chat transcripts, then merges their findings into a brief with capsule, thread statuses, problems, and next move.

How to find where I left off on a feature or bug?▼

Name the feature, file, or bug and the Skill mines your chat history plus the shared record of user reports, shipped fixes, and incidents. It verifies PRs and branches with git and gh before reporting current state.

Does recall work with Cursor chat transcripts?▼

Yes, it reads Cursor agent transcripts stored as JSONL under ~/.cursor/projects/<slug>/agent-transcripts/. Subagents order candidates by modification time and read only relevant regions of matching chats.

Can recall search issue trackers and error tracking tools?▼

Yes, when the topic names a feature or bug it delegates to the why skill's source investigators covering source control, issue trackers, chat channels, docs, and error tracking. Unavailable MCP sources are skipped and noted.

When should I not use recall for session context?▼

Skip it when resuming one specific prior chat, which is the session-pickup playbook, or when the user already provided a full state capsule with paths, branch, and the change. Pure activity summaries also skip the shared-record sweep.

Related Skills

Explore More Software Engineering Skills→
gmackiegmackie

recall

Reconstruct recent working context from chat transcripts and shared records into a current-state brief.

Community
Advanced
dot-dodot-do
2

workflow-status

Aggregate discovery.db briefs and beads epics into a single workflow view.

Official
Intermediate
jeremybrasherjeremybrasher

why

Investigates design rationale behind code by querying git history, tickets, docs, chat, and observability sources in parallel.

Community
Advanced
jnyrossjnyross

recall

Reconstruct recent working context from chat history and shared records into a status brief.

Community
Advanced