learn

You can manage project learnings across sessions by parsing and updating local knowledge stored in the gstack learnings store. This prevents repeating mistakes and speeds up onboarding by capturing, organizing, and recalling notes.

You can search and prune stale knowledge management entries using the /learn search command with a specific query, or batch remove conflicting data with the /learn prune command to keep your learnings store accurate.

Yes, you can manually add new learnings with the /learn add command and view stats to gauge coverage. This allows you to log notes directly and track the volume of stored knowledge.

The best way to export project learnings to project docs is using the /learn export command. This batch operation reads your local learnings data and formats it for external documentation.

Grouping recent learnings by type helps identify patterns in software engineering by structuring session notes into categorized views. This makes it easier to spot recurring issues and track knowledge trends over time.

Yes, you need the gstack tooling to store and recall session learnings. The skill reads and updates local learnings data directly through the gstack environment to manage your knowledge base.