memory-digest ยท diff
git:20260515.bd5cd95 to git:20261017.57ee451
4 added, 12 removed. Audit A to A.
---
name: memory-digest
description: Digest recent tape anchors and session context into curated pi-memory-md memories when tape mode is enabled. Use only with tape mode enabled when the user asks to summarize recent work, extract learnings, preserve decisions, convert tape/session history into memory, or review recent intent for durable memory updates.
---
# memory-digest
Turn recent tape anchors and nearby session context into concise, durable memory. Prefer curation over transcript summarization.
## Core rule
- Inspect recent intent first, read only relevant context, propose memory changes, then write only after user confirmation using the `memory-write` skill.
+ Inspect recent intent first, read only relevant context, propose memory changes, then write only after user confirmation.
- Keep each proposed memory focused on one durable topic.
- Keep proposal details lightweight: explain only why each candidate should be created, updated, or skipped.
- For possible updates, identify the existing memory file and briefly state why it should change.
- - Defer final description, tags, frontmatter shape, timestamp handling, and file creation/update mechanics to the `memory-write` skill.
+ - Use the [frontmatter format](../../README.md#memory-file-format): a concise `description`, lowercase string-array `tags`, and `created`/`updated` dates (`YYYY-MM-DD`). Preserve `created` when updating.
## Workflow
1. Inspect recent anchors with `tape_search({ kinds: ["anchor"], limit: 20, contextLines: 1 })`.
2. Infer the user's recent intent from handoff anchor names, summaries, purposes, keywords, timestamps, and nearby context.
3. Select the smallest useful tape range by combining anchor count and recency:
- Use `tape_search({ kinds: ["anchor"], anchorType: "handoff", anchorScope: "project", betweenDates: { start, end }, limit: 20 })` for handoff anchors from the last 2 days.
- Use `tape_search({ kinds: ["anchor"], anchorType: "handoff", anchorScope: "project", limit: 10 })` when recent date-filtered handoff anchors are not enough to capture the active thread.
- Use `tape_read({ betweenAnchors })` when a clear start/end pair exists.
4. Extract durable memory candidates only when they are useful across future sessions.
5. Compare candidates with existing memory using `memory_check({ directory })` or `memory_search` before proposing creates or updates. Then read the specific memory file if needed.
- 6. Apply the `memory-write` skill rules before showing proposed paths:
- - Treat `memory-write` as the single source of truth for placement, filename conventions, and frontmatter shape.
- - Validate every proposed relative path against `memory-write` rules.
- - Do not invent root folders or naming schemes outside `memory-write`.
- - If the correct path is uncertain, propose the candidate without a final path and ask the user to choose or confirm placement.
+ 6. Verify the memory directory with `memory_check` before proposing paths. Reuse existing topic folders; place always-needed project context in `core/project/`, never a root-level `project/` folder. Ask when placement is uncertain.
7. Present proposed changes and ask for confirmation.
- 8. After confirmation, use the `memory-write` skill to create or update memory files.
+ 8. After confirmation, use native `write`/`edit` tools. Read existing files before updating, preserve frontmatter, and refresh `updated`.
9. Ask before `memory_sync` unless the user explicitly requested sync.
## Save candidates
Save concise knowledge in these categories:
- user preferences
- project decisions
- architecture constraints
- reusable implementation patterns
- recurring bugs and fixes
- workflow habits
- unresolved questions or future directions
Do not save:
- raw command output
- temporary debugging noise
- one-off implementation details recoverable from git
- unconfirmed guesses
- large chat summaries
- secrets, credentials, tokens, or `.env` content
## Proposal format
Before writing, respond with:
```md
# Proposed memory updates
## Create
- `path/to/file.md`
reason:
## Update
- `path/to/file.md`
reason:
## Skip
- item:
reason:
```
End by explicitly asking the user for confirmation with: `Proceed with these memory updates?`
-
- ## Related skills
-
- - `memory-write`: Create or update memory files with valid frontmatter.