菜单
Mine project files or conversations into the MemPalace memory system. Indexes source code and conversation history as searchable palace drawers with semantic embeddings and room assignment.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | memory-mine |
| description | Mine project files or conversations into the MemPalace memory system. Indexes source code and conversation history as searchable palace drawers with semantic embeddings and room assignment. |
| user_invocable | true |
| metadata | {"author":"dimetron","version":"1.0"} |
Use this skill when the user wants to:
Runs pi memory mine to walk a directory and ingest files as palace drawers:
Source mining (default): Walks the directory tree, chunks source files (1500 chars, 200 overlap), assigns rooms via mempalace.yaml patterns or directory structure, generates embeddings, deduplicates (cosine >= 0.9), and stores as drawers.
Conversation mining (--convos): Parses JSONL (pi-go or Claude Code format) and plaintext conversations, pairs user+assistant turns, and stores as drawers with importance=4.
palace.db exists (run pi memory init . if not)pi memory model download if not)# Mine source files from current directory
pi memory mine .
# Mine source files with explicit wing name
pi memory mine . --wing my-project
# Mine conversation files
pi memory mine ./conversations --convos
pi memory status to confirm the updated stateThe user can pass arguments after /memory-mine:
. current directory)--wing <name> to override the wing name--convos to mine conversations instead of source filesExamples:
/memory-mine — mine current directory/memory-mine ./src — mine the src directory/memory-mine ./chats --convos — mine conversation filespi binary must be built and available (go build -o pi ./cmd/pi)pi memory init .)pi memory model download).gitignore patternsnode_modules, vendor, .git, build, targetmempalace.yaml for room assignment if presentIndex a folder's contents into the MemPalace semantic memory for search and retrieval. Use this skill whenever the user asks to "index a folder", "index a directory", "index memory", "mine a project into memory", "make a folder searchable", "embed a folder", "ingest code into the palace", or "index this directory for semantic search". Covers the full flow: model download, mempalace.yaml room configuration, mining, and verification via search. Also trigger when the user says "memory index", "index memory of folder", or asks how to make a project's code semantically searchable with pi-go's MemPalace.
Lazy senior dev mode — always pick the simplest solution that works. Use this skill whenever writing, refactoring, or reviewing code to keep changes minimal: prefer the standard library, native platform features, and already-installed dependencies over new code or dependencies. Trigger when the user says "ponytail", "keep it simple", "simplest thing that works", "don't over-engineer", "lazy mode", or asks to avoid unnecessary abstractions, boilerplate, or premature complexity. The best code is the code never written.
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass
Go 1.24–1.26 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2 configuration, slog logging, and manual dependency injection with functional options. Always consult this skill before generating Go code for pi-go, even for small snippets, to ensure every output is idiomatic and modern.
Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.