What problem does it solve? Valuable problem-solving patterns discovered during Claude Code sessions are lost when the session ends, forcing users to repeatedly rediscover the same fixes, workarounds, and debugging techniques. ## Core Features & Use Cases - Automatic Session Evaluation: Runs as a Stop hook at the end of each session, checking whether the session has enough messages (default 10+) to be worth analyzing. - Pattern Detection and Extraction: Identifies reusable patterns such as error resolutions, user corrections, workarounds, debugging techniques, and project-specific conventions, then saves them to ~/.claude/skills/learned/. - Configurable Behavior: A config.json file controls minimum session length, extraction threshold, auto-approval, and which pattern types to detect or ignore. - Use Case: After a long debugging session where you fixed a tricky framework quirk, the Stop hook automatically captures that workaround as a learned skill so future sessions can reuse it without re-deriving the solution. ## Quick Start Add the Stop hook entry pointing to evaluate-session.sh in your ~/.claude/settings.json file and adjust config.json to choose which pattern types should be extracted.
