session-gate

Validating MEMORY.md structure at session boundaries involves checking headings, timestamps, and template rules. This skill performs 18 deterministic mechanical validations using read-only analysis and git state, ensuring memory consistency without modifying user data.

Memory consistency validation for markdown session files is a read-only quality assurance process that detects structural drift in MEMORY.md. It checks defined template rules, headings, and last/next session timestamps to surface guidance without blocking the session.

Yes, you can run non-blocking quality assurance checks on MEMORY.md. The validation executes as advisory, read-only checks that surface results without blocking sessions, and can trigger an audit workflow when issues are detected.

No, session-gate does not modify user data during markdown validation. It implements deterministic checks using read-only analysis and git state to enforce mechanical integrity of MEMORY.md, applying validation at session gates and explicit invocations.

The best way to enforce memory template rules without blocking sessions is to apply advisory, read-only validation at session boundaries. This skill detects structural drift in MEMORY.md and surfaces actionable guidance, triggering an audit workflow only when issues are found.

You need to check MEMORY.md integrity for session management at session boundaries and through explicit invocations. This prevents drift and ensures memory consistency by validating structure against defined template rules, catching issues before they compound across sessions.