How It Works
Explain how claude-dejavu detects antipatterns and learns rules. Use when the user asks "how does dejavu work?" or "what is this thing doing?".
Install
$ agentstack add skill-cmg8431-claude-dejavu-how-it-works ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-cmg8431-claude-dejavu-how-it-works) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
How claude-dejavu works
Explain the following to the user:
What it does
claude-dejavu watches your Claude Code sessions for repeated mistakes. When it detects a pattern — like the same error happening across sessions, or code being reverted back and forth — it creates a rule and patches your CLAUDE.md so Claude doesn't make that mistake again.
The 3-step loop
[Session Logs] [Pattern Detection] [Rule Suggestion]
tool usage data ──▶ antipattern detectors ──▶ CLAUDE.md patch
▲ │
│ [Effectiveness Tracking] │
└────── rule fire counting ◀─────────────────────┘3 Detectors (v0)
- Revert Cycle — Claude edits a file, then someone reverts it, then Claude edits it again. Sign that Claude isn't checking existing logic before changing things.
- Repeated Error — The same error message keeps appearing across sessions (e.g., "command not found: npm" in a pnpm project). Claude keeps falling into the same trap.
- Silent Fix — Claude finishes work, then the user quietly edits the same file without saying anything. The user is correcting Claude's output through action, not words. This is the killer feature that differentiates dejavu from other tools.
Where data lives
- Rules database:
~/.local/share/claude-dejavu/dejavu.db(SQLite) - Session buffers:
~/.local/share/claude-dejavu/buffers/(temporary) - Output:
CLAUDE.mdin your project root
Rule format in CLAUDE.md
- This project uses pnpm, not npm. Run pnpm install not npm install.
↳ Learned from 4 repeated errors across 3 sessions.The HTML comments are metadata that Claude ignores but dejavu reads/writes for tracking.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: cmg8431
- Source: cmg8431/claude-dejavu
- License: MIT
- Homepage: https://www.npmjs.com/package/claude-dejavu
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.