oliver-kriska/claude-elixir-phoenix / targets/dsh/skills/phx-recall
phx-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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.4 KB |
| references/archaeology-patterns.md | markdown | 2.1 KB |
references/archaeology-patterns.md
View on GitHub# Archaeology Patterns
## Git recipes (Layer 2)
| Question shape | Recipe |
|----------------|--------|
| "When did we change/add X?" (code symbol) | `git log -S "X" --oneline` — pickaxe finds commits where the count of X changed |
| "Why does this line exist?" | `git log -L {start},{end}:{file}` or `git blame -w -C {file}` |
| "What happened to this file?" | `git log --follow --oneline -- {file}` (survives renames) |
| "What did we do about {topic}?" | `git log --grep="{topic}" -i --oneline` |
| "What changed between releases?" | `git log v2.10.0..v2.11.0 --oneline` |
| Inspect a candidate | `git show {hash} --stat`, then `git show {hash} -- {file}` for the diff |
Prefer `--oneline` + targeted `git show` over dumping full diffs into
context — same delta-only discipline as the watch-pr skill.
## ccrider query patterns (Layer 3)
- Lead with the concrete noun: `"form save silent changeset"` beats
`"debugging problem form"`
- Search returns ranked hits with session IDs + snippets — that's usually
enough to pick ONE session worth fetching
- `list_recent_sessions` when the user says "last week" / "yesterday"
rather than describing content
## Subagent prompt template (Iron Law 2)
One session per subagent — `get_session_messages` responses are 3–15KB
and batching floods the parent context:
```
Fetch session {SESSION_ID} via mcp__ccrider__get_session_messages.
The question is: "{QUESTION}"
Extract ONLY content that answers it: the problem, the fix/decision,
file paths, and the outcome. Ignore everything else.
Write at most 30 lines of markdown to .claude/recall/{SESSION_ID}.md
and reply with just "done" — the file is the output.
```
Note: ccrider messages use `type` (not `role`) and content is plain
string — tool usage must be inferred from assistant text.
## When all three layers miss
Say so explicitly: "No prior work found on {topic} in solution docs, git
history, or indexed sessions." A clean miss is a valid answer — do not
pad it with speculation. Suggest `/phx-compound` after the user solves it
fresh, so the next recall hits Layer 1.
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: 472k | 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: 198k | 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: 198k | 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: 198k | Updated | Claude CodeCodex | Verified | Install |