context-cache

To save conversation history for debugging, you can append context entries to a single diff-friendly markdown file. This preserves a complete narrative across sessions using an append-only model with consistent separators and standard headers.

An append-only context cache is a single file that records conversation history without deleting past entries. You need it during refactoring, feature development, or auditing to maintain a coherent, incremental history across sessions.

To format conversation logs to be diff-friendly, use consistent separators and a simple file structure with a standard header per entry. This enforces an append-only model that enables easy diffs and reviews without breaking history.

Yes, you can use a single file to track feature development decisions over time. The cache uses a deterministic path like docs/cache/DD-MM-YY_AppName_SummaryWord.md and supports an append-only history so entries are added but never deleted.

A limitation of using a single diff file for conversation context is that the append-only model means entries are never deleted, which can cause the file to grow large over time. It relies on a fixed path and simple structure to remain self-contained.

No, the context-cache skill requires no external dependencies to work. It is self-contained, meaning the reader can understand the context without external tools by using a fixed path and standard headers for each entry.