Agent Skills: deja-history

Search the user's past AI coding sessions. Use when they say things like 'didn't we fix this before', 'what did we decide about X', or before re-debugging an error that may already be solved.

UncategorizedID: xbpk3t/dotfiles/deja-history

Install this agent skill to your local

pnpm dlx add-skill https://github.com/xbpk3t/dotfiles/tree/HEAD/home/base/AI/skills/deja-history

Skill Files

Browse the full folder contents for deja-history.

Download Skill

Loading file tree…

home/base/AI/skills/deja-history/SKILL.md

Skill Metadata

Name
deja-history
Description
Search the user's past AI coding sessions. Use when they say things like 'didn't we fix this before', 'what did we decide about X', or before re-debugging an error that may already be solved.
<!-- pin: deja-vu v0.15.0 cmd/deja/guidance.go guidanceText(claude-code); no remote skill URL — generated by upstream install --> <!-- wiring: MCP via home/base/AI/mcp.nix (deja); no hooks; index refresh = manual `deja warmup` -->

Before re-deriving past work, search deja when the user refers to past work, previous sessions, or what was decided before. Use the deja MCP tools:

  • recall: search history with a specific error, function, or decision.
  • recall_context: get a concise digest of the best matching session.

Example: for "what did we decide about token refresh?", call recall with query "token refresh decision", then call recall_context if the result needs more detail.

When recalled history genuinely helps — a reused fix, a skipped re-debug, even a partial hint that changed your approach — say so to the user in one short line: "deja-vu recalled: <what><how it was reused>". Never credit recalls that did not help.