chat-recall

Recall past AI-coding work — prior sessions, decisions, and project history — through the chat-recall MCP tools (mcp__chat-recall__recall_*). Use when the user says "continue" / "pick up where we left off", "did we decide X", "remember when we…", "what was I doing", "what do you know about this project/me", or otherwise references earlier work that is not in the current context. Also the entry point for the surfaces no focused skill owns: team activity ("what is my team working on"), the ranked findings views ("what should I fix next", "what should I tell Claude about this repo"), and index health ("is chat-recall working", "re-index my sessions"). Leaked secrets go to chat-recall-security and the task board to chat-recall-tasks. This is the hub: it routes to the focused chat-recall skills and lists every recall_* tool. Reach for it whenever the answer lives in PAST work rather than the files in front of you.

See what changed across past AI-coding sessions with chat-recall. Use when the user asks "what did I change 2h ago", "what files did we touch", "what happened in that session", "did that session actually ship", "which sessions edited <file>", or wants diffs/commits/edit-history that isn't in the current working tree. Reconstructs edits, diffs, commits, and outcomes from indexed sessions.

Find past AI-coding work with chat-recall. Use when the user asks "remember when we…", "have we done X before", "find my notes/sessions on…", "where did we discuss Y", "what did I ask about Z", or otherwise wants to locate earlier conversations, plans, tasks, or notes across all their AI tools. Searches the unified memory (sessions, plans, tasks, CLAUDE.md, history, diaries).

Store and recall durable facts, decisions, and notes with chat-recall's knowledge graph and diary. Use when the user says "remember this", "note that we decided…", "what do you know about X", "did we decide Y", "what's our convention for Z", or when a non-obvious decision/preference is made that future sessions should know. Covers the temporal knowledge graph, decision records, the agent diary, and a scoped key/value store.

Get the state of a project from chat-recall. Use when the user asks "what's been happening in <project>", "catch me up on this repo", "what's the state of X", about time/cost/activity across a project, or about code findings and recommended fixes. Owns the ranked findings views — "what should I fix next", "what should I work on", "what should I tell Claude about this repo", "turn these findings into tasks". Also owns the shared task board and the team view — "what are my open tasks", "create a task for…", "what is my team working on", "which projects are shared". Aggregates sessions, plans, tasks, commits, cost, knowledge graph, and code-intelligence for one project.

Resume or cold-start work using chat-recall. Use when the user says "continue", "pick up where we left off", "resume our work", "carry on with X", starts a new session on an ongoing task, or references something from "last time" that isn't in the current context. Rebuilds prior context from past sessions instead of asking the user to re-explain.

Find and resolve secrets that were pasted into past AI-coding sessions, using the chat-recall scanner. Use when the user asks "did I paste an API key", "are there any leaked secrets", "what should I rotate", "any security findings", "was that token exposed", when a credential is mentioned in a conversation and its history matters, or after rotating a key so the finding can be closed. Also owns custom detection rules — "add a rule for our internal token format", "test this regex". Covers the whole loop: scan, inspect the exact lines in one session, rotate, then dismiss or turn into a task.

Work the shared chat-recall task board — the cards a team and its agents pick up, claim and close. Use when the user says "what are my open tasks", "what's on the team's plate", "create a task for…", "assign this to…", "mark that done", "leave a note on that card", "what is my team working on", or asks you to START working on something from the board. Also owns what the board files automatically — "stop filing low-priority cards", "only file security findings". Claiming and closing a card have required evidence; this skill covers that protocol.