memory-keepinglisted

Close out a pg-claude session — sync progress/STATE.md, progress/coverage.md, progress/files-examined.md, and append a sessions/ log entry whenever a session produced durable output (a new knowledge/idioms or knowledge/subsystems doc, a [verified-by-code] fact, a discovered gotcha, a file-by-file deep read, or a locked decision from pg-claude-plan.md §14). Use proactively when the user says "wrap up", "close out the session", "sync memory files", "record this gotcha", "we're done for the day", or "log this for next time" — and whenever durable output was just produced. Skip for PG MemoryContext / palloc / pfree internals questions (use memory-contexts), LangChain / LangGraph / LlamaIndex agent memory and vector stores, application memory leaks / valgrind / heaptrack, conversational chat history persistence, finding old Claude sessions (use find-session), and ChatGPT / Claude.ai conversation export.
matejformanek/postgres-claude · ★ 0 · AI & Automation · score 70

Install: claude install-skill matejformanek/postgres-claude

# memory-keeping The pg-claude system is only as useful as its memory. STATE.md, coverage.md, and the sessions/ log are how a future Claude (or future you) picks up cold without re-reading the whole repo. ## Invariants 1. **STATE.md is the front page.** It must answer in under a minute: what phase are we in, what's the last thing that got finished, what's the next concrete step. Keep it short — link to detail elsewhere. 2. **coverage.md is a table.** One row per documented artifact (subsystem, idiom, data-structure). Columns: `name | path | last-verified-commit | confidence-summary | open-questions`. 3. **sessions/ is append-only.** One file per significant session, `YYYY-MM-DD-<topic>.md` (use **today's** date, the day you're writing — not the date of the work if it spanned multiple days). Never edit old session logs; if a later session invalidates a claim, write a new session log that supersedes it and update STATE.md to point at the newer one. 4. **files-examined.md is the per-file ledger.** Append-only. One row per source file read in non-trivial depth, columns: `path | depth (skim/read/deep-read) | date | last-verified-commit | produced-doc`. Append whenever a file becomes load-bearing for any claim in `knowledge/`, including pure file-by-file deep reads that don't yet have a synthesis doc. (See CLAUDE.md rule 6: "Track what you read.") ## When to update what | Trigger | STATE.md | coverage.md | files-examined.md | sessions/ | |--