/memory-why

Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.

ferroxlabs@ferroxlabs

GitHub

From plugin

ijfw

20522 skills37 agents22 commands1 MCP

Install

$ npx -y skills add FerroxLabs/ijfw --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/memory-why

Context preview

What this command does when you run it.

Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.

Command definition

memory-why.md

description: "Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance."
allowed-tools: ["Read", "Bash"]

For a given recall, report which signals contributed. Agent prompt:

When the last `ijfw_memory_recall` / `ijfw_memory_search` call returned a hit, surface:

<match-id>
  BM25:       <score>   (matched terms: <tokens>)
  vector:     <cosine>  (model: <model or "disabled">)
  combined:   <merged score>
  snippet:    <first 160 chars>

If vectors are disabled (`IJFW_VECTORS=off` or library not installed): say *"Vectors disabled; result from keyword match only."* rather than showing a 0 cosine that looks negative.

Use this to debug why a recall did (or didn't) find something the user expected.

Read it on GitHub ↗

Ships withijfw

IJFW — It Just F*cking Works. Ferrox Labs' local-first infrastructure for AI coding agents: shared memory, smart routing, multi-AI cross-audits, disciplined workflow.

Get the whole plugin

Stats

JavaScript Node React Bash PowerShell

+6 tags

Git GitHub Markdown Anthropic Gemini MCP

205

Stars

Forks

Active

Maintenance

JavaScript

Language