oliver-kriska/claude-elixir-phoenix / plugins/elixir-phoenix/skills/recall
recall
VerifiedRecall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.
Recall — Session & History Archaeology
Search three evidence layers, cheapest first, to answer "have we solved this before?". Stop at the first layer that answers the question.
Usage
/phx:recall how did we fix the LiveView form that saved silently?
/phx:recall what did we decide about the billing context boundaries?
/phx:recall which library did we pick for rate limiting and why?
Iron Laws
- Cheapest layer first — solution docs (local grep) → git history → session transcripts. Don't fetch sessions when a solution doc answers
- ONE ccrider fetch = ONE subagent —
get_session_messagesresponses are 3–15KB each. Spawn a subagent per session that writes a summary file and exits; NEVER batch multiple session fetches into one context - Cite the evidence — every claim names its source (solution doc path, commit hash, or session date + match snippet). No vague "we did this once"
- Graceful degradation, stated plainly — if ccrider MCP is absent, say so once and use the fallback layers; never error out
Workflow
Layer 1: Compound Solution Docs (always)
Run Grep with keywords from the question over .claude/solutions/.
Treat a hit here as the best answer — it was written for exactly this
purpose. Present it and stop unless the user wants more.
Layer 2: Git Archaeology (always available)
git log --oneline --grep="{keyword}" -i -20 # commit messages
git log -S "{code-symbol}" --oneline -10 # when a symbol changed
git log --follow --oneline -10 -- {file} # one file's history
git show {hash} --stat # inspect a candidate
Use -S (pickaxe) when the question names code; --grep when it names
intent. Show matching commits with one-line context each.
Layer 3: Session Transcripts (ccrider MCP, gated)
Check for mcp__ccrider__* tools (load via ToolSearch if deferred).
If absent: report "ccrider MCP not connected — answered from solution docs + git history" and stop after Layers 1–2.
If present:
mcp__ccrider__search_sessionswith the question's key phrases — returns ranked hits with session IDs and snippets- Present the top 3–5 hits (date, snippet) and pick the most relevant (or ask, if genuinely ambiguous)
- Per selected session, spawn ONE subagent: "Fetch session {id} via
mcp__ccrider__get_session_messages, extract only what answers '{question}', write ≤30 lines to.claude/recall/{id}.md" (Iron Law 2) - Read the summary files, synthesize the answer with citations
Step 4: Answer + Compound
Present the answer with its evidence trail. If the recalled knowledge was
NOT already in .claude/solutions/, offer /phx:compound so the next
recall stops at Layer 1.
Integration
"have we done this before?" → /phx:recall
Layer 1 .claude/solutions/ ──hit──► answer + cite
Layer 2 git log --grep/-S ──hit──► answer + cite
Layer 3 ccrider sessions (gated) ─► answer + cite → offer /phx:compound
References
${CLAUDE_SKILL_DIR}/references/archaeology-patterns.md— git pickaxe recipes, ccrider query patterns, subagent prompt template
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 197k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |