continuous-learning

You can extract reusable patterns from Claude Code session transcripts by using a Stop hook that analyzes the full session at completion, detecting patterns like error resolution and debugging techniques, then saving them as learned skills.

Yes, you can automatically save debugging techniques and error resolutions by enabling a continuous learning Stop hook that detects these specific patterns in the transcript and stores them in a dedicated learned skills directory.

You configure pattern detection thresholds by modifying the config.json file, which controls minimum session length, detection thresholds, and the specific patterns to extract such as user corrections and project-specific workarounds.

Continuous learning requires no external dependencies to start harvesting skills; it operates as a Stop hook within the Claude Code environment and writes extracted patterns directly to the local file system.

The best way to filter out short sessions is by setting a minimum session length parameter in the config.json file, ensuring the Stop hook only analyzes substantial transcripts that contain meaningful repeatable patterns.

Learned skills extracted from Claude Code transcripts are stored in the ~/.claude/skills/learned/ directory, making them available as reusable resources for future coding sessions.