recall-reasoning
FeaturedRecall the reasoning behind a past change by locating the Claude Code transcript that produced it. Use when the user asks to "recall reasoning", "find reasoning", "look up reasoning", "recall implementation reasoning", "find the rationale", "why did I do X", "recall from transcripts", or "find the transcript for this commit".
Install
Quality Score: 89/100
Skill Content
Details
- Author
- tobihagemann
- Repository
- tobihagemann/turbo
- Created
- 6 months ago
- Last Updated
- 2 days ago
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
rh-recall
Search everything already worked out — past session transcripts, scribe rows and their LLM proposals, shared learnings, per-project memory, and the concept graph — before deriving something from scratch. Use when a question sounds like it may have been answered in an earlier session, when starting work in an unfamiliar area, or when the user references a prior decision.
recall
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.
session-recall
Search the unified local history of past Claude Code and Codex sessions at the START of a task when the user references a prior bug, feature, decision, file, or piece of work. Use before assuming fresh context for prompts such as "remember when…", "we worked on…", "the X bug", "back to…", "what did we decide about…", or any task that plausibly has history.