kb

To save conversation insights to a markdown knowledge base, use the kb upsert feature to write new findings or update existing topics with timestamps in a structured Markdown file.

Upserting a knowledge base works by reading the project name from your directory and using a shell script to create or update sections in a Markdown file, preserving decisions and critical context with timestamps.

Yes, you need ripgrep installed as a dependency to manage project notes and documentation, because the upsert scripts rely on it for searching and updating the structured Markdown knowledge base.

Yes, you can update existing topics in a knowledge base without losing history, because the upsert process automatically adds timestamps to revised conclusions and preserves previous decisions within the structured Markdown file.

The best way to keep feature development learnings in sync is to upsert key information by topic into a centralized knowledge base, ensuring critical context and decisions are never lost during planning.

A knowledge base upsert may not write to the correct project file if the local configuration in ~/.kb/config.json is missing or if the current project name cannot be read from the directory.