dist/claude/plugins/dev-tools/skills/mem-history/SKILL.md
Query project history, past decisions, and known gotchas from claude-mem observations. Use when user asks "last session", "did we already", "what did we decide", "project history", "timeline", or "what happened with".
npx skillsauth add alexei-led/claude-code-config mem-historyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Query cross-session history via claude-mem.
Searches observations stored by claude-mem in the current project only. Does not access git history, file contents, or observations from other projects.
See also learning-patterns for encoding new observations.
Tell the user that cross-session memory requires the claude-mem plugin (/plugin install claude-mem@thedotmack). Suggest alternatives: check git log for recent changes, read CLAUDE.md files for project context, or use git blame for file history.
search with keywords — returns compact list with IDs (~50-100 tokens/result)get_observations with IDs from search — returns full narratives (~500-1000 tokens/result)timeline with anchor ID or query — shows chronological context around an observationsearch with file path or feature namesearch with approach keywordssearch → get_observations on relevant IDssearch type filter for gotchas/problem-solutiontimeline with broad queryAND, OR, NOT, quoted phrasesgotcha, problem-solution, decision, discoveryPresent findings as a concise list ordered by recency:
MEMORY RESULTS: {query}
=======================
[date] {type} — {summary} (ID: {id})
[date] {type} — {summary} (ID: {id})
If nothing found: "No observations found for '{query}'. Try broader terms or check git log."
tools
Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview. NOT for generic implementation planning that does not read or write `.spec/` files.
development
Simple web development with HTML, CSS, JS, and HTMX. Use when working with .html, .css, or .htmx files, web templates, stylesheets, or vanilla JS scripts. NOT for React/Vue/Angular (use writing-typescript) or Node.js backends.
tools
Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or TypeScript design advice. Emphasizes strict typing, boundary validation, composition, fast feedback, behavior tests, and project-configured tooling. NOT for Go, Python, Rust, plain HTML/CSS/JS, or server-rendered templates (use writing-web).
tools
Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, CI `run:` shell bodies, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, Rust, TypeScript, Go, web code, or GitHub Actions workflow/job/permissions semantics; use operating-infra.