continuous-learning

You can automatically extract reusable patterns from Claude Code sessions by running a Stop hook that analyzes session activity and saves identified error resolutions and debugging techniques as learned skills.

A Stop hook captures learned skills by evaluating the completed session at the end, identifying repeatable workarounds, and persisting them as files in the .claude/skills/learned/ directory for future reuse.

Yes, you can configure which session patterns get extracted by using a config.json file to define specific patterns_to_detect and set ignore_patterns to filter out unwanted session data.

Extracted session patterns and workarounds are saved directly to the .claude/skills/learned/ directory, ensuring that captured debugging techniques and error resolutions are available for reuse across projects.

The types of debugging techniques harvested from a completed coding session include effective error resolutions, temporary workarounds, and successful debugging patterns that proved useful during the workflow.

No dependencies are needed to start saving Claude Code session learnings automatically, as the skill operates independently as a Stop hook to analyze sessions and write extracted patterns to the learned directory.