session-learnings

To capture project knowledge across sessions, use custom bash scripts to log insights, types, and confidence levels, then retrieve them later to avoid repeating mistakes and improve workflow efficiency.

Tracking session learnings for debugging involves logging the root cause and resolution strategy as an entry, preventing similar future issues by making past resolutions searchable for subsequent debugging sessions.

To log a specific learning after resolving an error, execute the logging script with parameters for type, key, insight, and optional confidence, source, and files to store the knowledge.

Yes, you need bash to run this knowledge management workflow because the logging and retrieval mechanisms rely entirely on custom shell scripts to store and search project insights.

You can search past learnings before starting a new coding session by running the search script, which retrieves stored project knowledge to inform current decision-making and enhance productivity.

Using shell scripts for knowledge capture limits complex querying and structured data relationships, as the system relies on custom bash scripts rather than a dedicated database for managing project insights.