continuous-learning

You can automatically extract reusable patterns from Claude Code session transcripts by configuring a Stop hook that triggers pattern evaluation at the end of each session, saving resolved error handling and debugging techniques locally for future reuse.

A Stop hook in Claude Code continuous learning is an end-of-session trigger that evaluates completed transcripts to detect meaningful development patterns, filtering sessions by minimum message count before saving them as local skills.

Yes, you need jq installed as a dependency to parse session transcripts and filter hook input, as the evaluation script relies on it to process the JSON environment context for pattern extraction.

Yes, you can control which Claude Code sessions get saved by configuring minimum message count thresholds and extraction strictness settings, which filter out low-value sessions and ignore patterns that lack reusable debugging or error resolution value.

The pattern extraction process targets development sessions that resolve errors, apply debugging techniques, create workarounds, or establish project-specific conventions, saving these categorized patterns into a configured local learned skills directory.

To set up automatic pattern extraction, add the provided Stop hook command to your ~/.claude/settings.json file so the evaluate-session.sh script runs automatically when a session ends, parsing the transcript and writing learned patterns to your configured path.