lcm

Lossless context management — search and store persistent memory across sessions

Lossless context management — search and store persistent memory across sessions

Use when deciding which lcm MCP tool to call — lcm_search, lcm_grep, lcm_expand, lcm_describe, lcm_store, lcm_doctor, or lcm_stats — or when an lcm tool returns an error.

Use when the user says 'cut a release', 'release vX.Y.Z', 'publish a new version', or 'bump the version'. Covers the full release flow: version bump → PR to main → CI → merge → publish → develop sync.

This skill should be used when the user asks to "run lcm dogfood", "self-test lcm", "validate lcm build", "test lcm hooks", "check lcm mcp tools", or mentions lcm QA, regression testing, or pre-release validation. Runs a comprehensive 39-check self-test across all CLI commands, hooks, MCP tools, and resilience.

You MUST use this before any work to recall project memory, and after implementing to store decisions. Lossless-claude (lcm) provides persistent cross-session memory via CLI commands.

Run the E2E validation checklist against a real lcm installation. Tests daemon, hooks, import, compact, promote, retrieval, and resilience. Pass a flow name for a subset (import, compact, promote, curate, retrieval, hooks, doctor, cleanup), or omit for the full suite.

Rebuild, reinstall, and restart lossless-claude from source. Fixes hooks, restarts daemon, runs diagnostics. Trigger: /lossless-claude:upgrade