memory-consolidate

Name: memory-consolidate
Availability: InStock
Author: gerardloupecyb

Detect semantic inconsistencies across MEMORY.md, LESSONS.md, and DECISIONS.md.

Updated Mar 1, 2026

Search Tags:#drift-detection #quality-assurance #read-only #memory-consolidation #project-documentation #cross-file #memory-coherence

Ready to run

npx skills add https://github.com/gerardloupecyb/claude-code-project-template --skill memory-consolidate-gerardloupecyb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory-consolidate
Source: https://github.com/gerardloupecyb/claude-code-project-template/tree/main/.claude/skills/memory-consolidate
Command: npx skills add https://github.com/gerardloupecyb/claude-code-project-template --skill memory-consolidate-gerardloupecyb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memory coherence across project memory files like MEMORY.md, LESSONS.md, and DECISIONS.md is verified to prevent semantic drift. This tool is read-only, advisory, and does not modify any files.

Core Features & Use Cases

Verifies semantic consistency across memory files to prevent drift and duplication.
Generates actionable insights for hygiene checks and cross-file references.
Use Case: before a release, run this skill to validate that memory notes align with decisions and lessons.

Quick Start

Run the memory-consolidate command to generate a coherence report without modifying any files.

Frequently Asked Questions about memory-consolidate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check memory coherence across project documentation files?▼

You can check memory coherence by running a read-only audit that detects semantic inconsistencies, duplicates, and open blocks across MEMORY.md, LESSONS.md, and DECISIONS.md. It provides an actionable summary without modifying any files.

What is semantic drift detection in project memory files?▼

Semantic drift detection identifies inconsistencies across MEMORY.md, LESSONS.md, and DECISIONS.md. It checks for misaligned dates, duplicates, open blocks, and broken cross-file references to ensure project documentation remains accurate.

Can I validate project memory before a release without altering the files?▼

Yes, you can validate project memory before a release without altering files by using a read-only quality assurance check. It reports findings and guidance on restoring coherence while ensuring no modifications are made to the documentation.

How do I find duplicate entries and broken cross-file references in markdown documentation?▼

To find duplicate entries and broken cross-file references in markdown documentation, apply read-only drift-detection checks. This generates an actionable summary highlighting inconsistencies to help restore memory coherence across the project.

What is the best way to prevent documentation drift in project memory files?▼

The best way to prevent documentation drift in project memory files is to perform regular read-only coherence audits. This identifies semantic inconsistencies, validates dates, and checks cross-file references to maintain alignment across MEMORY.md, LESSONS.md, and DECISIONS.md.