dist/pi/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.
Use local evidence. If no explicit memory provider is configured, do not pretend one exists. Pretend memory is called fiction.
Check, in order:
AGENTS.md, CLAUDE.md, GEMINI.md, CONTEXT.md, and docs/adr/.docs/plans/ and docs/plans/completed/.git log --oneline --decorate --max-count=20.git log -- <path> for specific files.git blame <path> only when line history matters.rg.rg -n 'decision|because|ADR|plan|migration|deprecated' AGENTS.md docs . 2>/dev/null
git log --oneline --decorate --max-count=20
git log --oneline -- path/to/file
## History
### Findings
- `path:line` or `commit` — fact
### Likely Decision
<grounded explanation>
### Gaps
- <missing evidence>
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.