skills.rest
oliver-kriska
oliver-kriskaCOMMUNITY
Explore all skills by this author →
Website𝕏@quatermain32GitHub

phx-recall

Searches solution docs, git history, and session transcripts to recall prior work.

537|38|Updated Feb 12, 2026
Search Tags:#Elixir#Recall#Phoenix#ccrider#knowledge search#Git history#session transcripts
One-click install
npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-recall
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: phx-recall
Source: https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/codex/skills/phx-recall
Command: npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-recall

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When working on long-running Elixir/Phoenix projects, teams often re-solve problems they already fixed in past sessions. This Skill answers "have we done this before?" by searching three evidence layers — local solution docs, git history, and session transcripts — so prior fixes and decisions are found instead of rediscovered.

Core Features & Use Cases

  • Layered evidence search: Checks .claude/solutions/ first via grep, then git history with pickaxe (git log -S) and --grep recipes, then ccrider MCP session transcripts as a gated fallback.
  • Context-safe transcript fetching: Spawns one subagent per session fetch so large get_session_messages responses never flood the parent context.
  • Cited answers with graceful degradation: Every claim names its source (doc path, commit hash, or session date), and if ccrider MCP is absent it says so once and answers from the first two layers.
  • Use Case: Ask "how did we fix the LiveView form that saved silently?" and get the prior fix with the commit hash or solution doc that recorded it, plus an offer to compound new knowledge for next time.

Quick Start

Ask the assistant to use the phx-recall skill to find how we previously fixed the silently failing LiveView form save.

Frequently Asked Questions about phx-recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find out if a bug was already fixed in a previous session?▼

Run the recall workflow with a question describing the bug. It greps local solution docs first, then searches git history with pickaxe and grep recipes, and finally queries ccrider session transcripts if that MCP is connected.

How to search git history for when a code symbol changed?▼

Use the pickaxe recipe `git log -S "symbol" --oneline` to find commits where the count of that symbol changed. For intent-based questions use `git log --grep="topic" -i`, and `--follow` for a single file's history across renames.

Does the recall workflow work without the ccrider MCP server?▼

Yes, it degrades gracefully. If ccrider MCP tools are absent it states that once and answers from solution docs and git history only, never erroring out on the missing integration.

Why does the skill spawn a subagent for each session transcript fetch?▼

Each get_session_messages response is 3-15KB, so batching multiple fetches would flood the parent context. One subagent per session writes a summary of at most 30 lines to a file and exits, keeping the main context small.

What happens when no prior work is found on a topic?▼

It reports a clean miss explicitly, stating that nothing was found in solution docs, git history, or indexed sessions. It then suggests compounding the fresh solution afterward so the next recall hits the first layer.

Related Skills

Explore More Software Engineering Skills→
DieStokDieStok

ce-sessions

Search and summarize coding agent session history from logs and metadata.

Community
Intermediate
kwam1nakwam1na

ce-compound

Create structured solution documents with YAML frontmatter under docs/solutions.

Community
Advanced
vasilievyakovvasilievyakov
17

learned-lessons

Record solved problems into a centralized Markdown knowledge base.

Community
Intermediate
opzero1opzero1
3

git-master

Automate advanced Git workflows including atomic commits, rebasing, and history search.

Official
Advanced