# Memory Mining

> Authoritative protocol for querying the Memory Core before diagnosing regressions or proposing non-trivial architectural claims. Prevents re-derivation of prior reasoning by surfacing cross-session, cross-harness context via semantic search. Triggers: Use this skill when (1) the user reports a regression symptom ("used to work", "suddenly broken", surprise validation failures, schema mismatches, "additionalProperties" rejections), OR (2) you are about to propose an architectural claim, roadmap, or comparison against external work where prior sessions may have already mapped the territory, OR (3) you are about to begin an implementation or a PR-review — a cheap 3–10-call prior-art sweep before the first design sentence or review verdict.

- Skill: `neomjs/memory-mining` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add neomjs/memory-mining`
- Raw SKILL.md: https://api.skillmd.com/api/skills/neomjs/memory-mining/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: neomjs (https://skillmd.com/u/neomjs)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/neomjs/memory-mining

---


# Memory Mining Skill

If you are diagnosing a regression symptom, about to propose a non-trivial architectural claim, or about to begin an implementation or a PR-review, you MUST immediately use the `view_file` tool to read and strictly adhere to `.agents/skills/memory-mining/references/memory-mining-protocol.md` before running `git log`, `grep`, the first design sentence, or a review verdict. Or, if you already have the payload in context, proceed directly to its directives.