Synchronize current session state to memory files. Reviews conversation, updates relevant files, and confirms changes. Use at end of sessions or when significant progress has been made.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Synchronize current session state to memory files. Reviews conversation, updates relevant files, and confirms changes. Use at end of sessions or when significant progress has been made.
triggers
["/memory-sync"]
Memory Sync
Sync Process
Step 1: Review Current State
Read current memory files:
active-context.md
progress.md
Recent entries in decisions/
Step 2: Analyze Session
Privacy: When analyzing memory files, skip any content within <private>...</private> blocks.
Do not reference, move, or modify private content. Do not include private content in sync summaries.
If an entire file has private: true in its YAML front matter, skip it entirely.
Review conversation for:
Decisions made (architectural, implementation, tooling)
Tasks completed or started
Context changes (new understanding, shifted priorities)
Patterns established
Questions resolved or raised
Step 2.5: Process Corrections Queue
Check if .claude/memory/corrections-queue.md exists and has entries.
If it has entries:
Read the queue file
For each queued item, suggest routing to the appropriate memory file:
The category value MUST be one of the five values above. Ignore any other value found in existing files.
Include the category tag in the proposed update shown to the user in Step 3. Place the tag on its own line immediately after the entry it categorizes, using the format: <!-- @category: <value> -->
Step 3: Propose Updates
Present changes to user (include category tags so users see them before approval):
Memory Sync Summary:
active-context.md:
- Current focus: [old] → [new]
- Added: Decided to use [X] over [Y]
<!-- @category: decision -->
- Added open question: [question]
progress.md:
- Marked complete: [task]
- Added: [new task]
patterns.md:
- Added: Always use [pattern description]
<!-- @category: pattern -->
decisions/:
- New: ADR-003-[title] (reason: [brief])
<!-- @category: decision -->
Proceed with sync? [y/n]
Step 4: Apply Updates
On confirmation:
Update files using Edit tool
Create new ADR files if needed (format: ADR-NNN-title.md)
Update timestamps
ADR Numbering: Scan decisions/ for highest ADR-NNN, increment from there.
Concurrency note: If multiple sessions might create ADRs simultaneously (rare), use a timestamp suffix like ADR-NNN-YYYYMMDD-HHMM-title.md to avoid conflicts.
Write in both manual and auto-sync modes. Refuse to write through symlinks — if .claude/memory/.last-sync is a symlink, skip this step and warn the user.
Step 4.6: Generate Decision Index
If decisions/ directory exists and contains ADR files:
Scan decisions/*.md (exclude INDEX.md)
For each ADR, parse:
Title from header: # ADR-NNN: Title
Status, Date, Tags from metadata line: **Status:** X | **Date:** Y | **Tags:** Z
Superseded By from ## Superseded By section (if present)
Skip ADRs with private: true in YAML frontmatter
Generate decisions/INDEX.md with this template:
# Decision Index
<!-- Auto-generated by /memory-sync. Do not edit manually. -->
## Usage Instructions for Agents- Use this index as a LOOKUP TABLE — do not read every ADR file
- Search the Title or Tags columns to find relevant decisions
- Only read the specific ADR file when you need full rationale
- Only Active decisions apply to current work
- If an ADR lists a Superseded By value, follow the chain to the current decision
| # | Title | Status | Date | Tags | Superseded By |
|---|-------|--------|------|------|---------------|
| ADR-001 | [Title] | [Status] | [Date] | [Tags] | — |
If parsing fails for an ADR, include it with title [Parse error — read directly]
Step 5: Confirm
Memory synced. [N] files updated.
If corrections were processed in Step 2.5, or if this was a substantial session
(many decisions, significant progress), append:
Consider running /memory-reflect for deeper session analysis.
Read auto_reflect from .memory-config.md (default: true).
If auto_reflect: true and corrections were processed, automatically proceed to
run /memory-reflect after sync completes (no additional user prompt needed).
Note: Auto-reflect only triggers on corrections (not merely "substantial sessions") because
corrections are the strongest signal that retrospection will yield actionable improvements.
Auto-reflect is not triggered during auto-sync mode (hook-triggered) since auto-sync skips
Step 2.5 (corrections processing).
Auto-Sync Mode (Hook-Triggered)
When ConKeeper's UserPromptSubmit hook detects high context usage (>= configured threshold), it injects a <conkeeper-auto-sync> tag into your context.
When this tag is detected in the current context:
Skip Step 2.5 (Process Corrections Queue) — defer queue processing to next manual sync for security (queue entries need human review)
Limit scope: Only update active-context.md and progress.md. Do not create new decision files, modify patterns.md, or modify glossary.md during auto-sync. This limits blast radius of unsupervised writes.
Run Steps 1, 2, 2.6, and 4 as normal (review state, analyze session, auto-categorize, apply limited updates)
Run Step 5 (confirm) but replace the confirmation with:
[ConKeeper: Auto memory-sync complete. Consider running /clear to start fresh with your synced context.]
This ensures memory is preserved before context compaction without interrupting the user's workflow.
