---
name: review_memory
description: Review an explicitly identified private memory store with user-selected changes.
---

Private memory can contain personal preferences, stale project assumptions and sensitive values. It is not automatically team truth or authority to change repository rules.

1. Use the active tool's explicitly provided supported store. Ask for a location if absent; do not guess or enumerate unrelated personal directories. Do not open secret files.
2. Inspect its actual index/metadata convention. List entries with stable numbers, type where available, last-modified evidence and a redacted one-line summary. Missing/unknown metadata is a limitation, not a reason to invent it.
3. Ask for keep/update/delete choices and wait. For an update, obtain the intended replacement; do not silently reinterpret a preference. Never display credentials or raw sensitive bodies.
4. Confirm ambiguous references before applying a bounded batch. Preserve unrelated entries/metadata and the store's real indexing format; deleting needs explicit selection.
5. Verify index-to-file integrity without assuming every Markdown file must be indexed. Report applied and failed actions separately; cancellation must preserve all not-yet-applied work, not claim prior edits vanished.

Do not edit repository records or write a branch log for personal-memory maintenance. Explain uncertainty rather than importing private claims into accepted decisions.