Dejavu — Development skill for Claude Code
Stop debugging the same bug twice.
How to install Dejavu
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open naveenspark/dejavu and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Dejavu does
Stop debugging the same bug twice. A Claude Code slash command for capturing, tagging, and retrieving debugging post-mortems.
Alternatives in Development
- Octo Debug — Systematic debugging with methodical problem investigation 2.8k ★
- Claudekit Debugging Tools — Debugging and troubleshooting tools 1.9k ★
- Apex Architect — Use the @apex-architect agent to help the user with the following architectural or debugging matter: $ARGUMENT 523 ★
README
Deja Vu
Persistent memory for Claude Code mistakes.
Claude Code forgets everything between sessions. You fix a mistake, close the session, start a new one, and Claude makes the same mistake again. Wrong approach. Ignored the docs. Confidently wrong about something it was confidently wrong about last time.
I started tracking these in a `LEARNINGS.md` file and it grew to hundreds of lines of painful lessons. I hoped Claude would pay attention to it, but it never did. Then I found [EveryInc's Compound Engineering](https://github.com/EveryInc/compound-engineering-plugin) plugin, which solves this exact problem. It's pretty neat, but it felt heavy: YAML schemas, category directories, npm packages. I wanted something simpler.
Deja Vu is two things:
/dejavuis a slash command you run after Claude screws up (and it will, over and over again). It captures what happened, tags it, and writes it toLEARNINGS.md.- "facepalm" is a word you type when Claude is doing something dumb again. Claude stops what it's doing, searches its file of shame for the relevant lesson, and course-corrects on the spot.
That's it. One file, freeform tags, and grep.
Install
# 1. Copy the slash command (capture mode)
cp dejavu.md ~/.claude/commands/
# 2. Create your learnings file
cp LEARNINGS-template.md ~/.claude/LEARNINGS.md
Then add this to your `CLAUDE.md` so Claude knows what "facepalm" means:
## Rules
When the user says "facepalm":
STOP. Something you're doing has been done wrong before.
Search ~/.claude/LEARNINGS.md for error messages, symptoms, or keywords
from whatever just went wrong. Show matching entries. If a past lesson
applies, follow it immediately.
Before starting any task, check LEARNINGS.md for relevant past mistakes.
Two behaviors, three files.
Usage
**After Claude screws up:**
/dejavu # Full reflection (5 questions)
/dejavu "auth migration" # Specific topic
/dejavu --quick
Related Skills
Investigator
Root-cause debugging specialist that diagnoses issues through systematic investigation before proposing any fi
Incident Commander
Incident Commander - structured incident response with severity assessment and blameless post-mortems
Incident Pattern Matcher
A Claude skill for SREs to identify recurring failure patterns across post-mortems and incident logs
Bug Race
Use when a bug has already survived at least one debugging attempt and you have 2-3 genuinely distinct root-ca
Stop Guessing
Debugging discipline for coding agents: reproduce, localize, evidence, minimal fix, verify. Never edit code to
Slow Claude
lowing Claude down is the feature, not the bug. A skill + slash commands enforcing disciplined feature develop
Related Agents
Gideon
Incident responder for production emergencies, crisis management, debugging, rapid fixes, and post-mortems. Us
Loom Advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an impleme
Ndv Diagnose
Debugging specialist. Use when you have a bug, failing test, stack trace, unexpected behavior, or anything bro