recall
FeaturedRecall this repository's OwnMem local memory before changing code, and keep it healthy. Use when a repository contains .ownmem/, when past debugging lessons could apply ("have we hit this before", "why is it done this way"), or when the user mentions ownmem, project memory, or recalling across sessions.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- grpcer
- Repository
- grpcer/ownmem
- Created
- 1 months ago
- Last Updated
- 4 days ago
- Language
- JavaScript
- License
- Apache-2.0
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
ownmem
Recall this repository's OwnMem local memory before changing code, and keep it healthy. Use when a repository contains .ownmem/, when past debugging lessons could apply ("have we hit this before", "why is it done this way"), or when the user mentions ownmem, project memory, or recalling across sessions.
recall-memory
Unified MEMORY recall + write (ADR-0004) — query or append to the project's memory store (JSONL by default, Obsidian vault or sqlite swappable). Use when resuming a project, when the user asks "what do we know about X", or when substantial work should be persisted for the next session.
memarium-recall
**TRIGGER IMMEDIATELY when the user's question contains retrospective phrasing in ANY language:** 之前是怎么解的 / 之前怎么解的 / 上次怎么处理的 / 上次怎么解决的 / 以前遇到过吗 / 以前我们怎么做 / 之前我们试过吗 / how did we fix X before / how was Y solved / why does Z work this way / what did we try last time / did we already try W. **Also trigger on:** design/architecture/prior-art questions — what pattern should I use for X / how have we approached Y before / what did we decide about Z / is there prior art for W. **Anti-pattern to break before reflex kicks in:** the question often contains clear keywords (file name, crash type, API) and your shortcut instinct is `git log --grep="<keyword>"` — DO NOT. Commit messages strip the conversation context where the user explained what didn't work and why; memarium's typed memory preserves decisions, dead ends, trade-offs, and unmerged-attempt context that git history can't surface. Run memarium-recall (one CLI call, ~small) FIRST; if nothing matches, *then* fall back to git. Two-stage recall over typed memory —