learner

To capture reusable insights from debugging conversations, run the learner command after solving a tricky bug. It distills practical heuristics from the discussion into a structured skill containing the Problem Statement, Solution, Triggers, and Scope for future reuse.

Saving non-obvious workarounds requires extracting contextual heuristics from your session and formatting them as structured guidelines. This process identifies the specific problem, the uncovered solution, and its scope, turning a temporary fix into a reusable knowledge artifact.

Yes, you can extract problem statements and solutions directly from chat history. The skill analyzes your conversation context to identify the core issue and its resolution, packaging them into a shareable guideline that informs future problem-solving tasks.

Creating context-aware guidelines from design decisions involves extracting the core heuristics from your conversation. It focuses on problems specific to your codebase and domain, producing a structured artifact that captures the trigger conditions and scope of the applied solution.

Capturing learned patterns requires no external dependencies. The skill operates independently to process your conversation context and output a structured guideline, ensuring the extracted heuristics are immediately ready for storage and reuse.

You should not use conversation insight extraction for generic programming problems that are not specific to your current codebase. The skill is scoped to capture domain-specific heuristics and non-obvious workarounds, so widely applicable external knowledge does not fit its extraction model.