What problem does it solve? Claude Code sessions generate valuable usage data that normally disappears when the session ends, so recurring friction points, workflow patterns, and knowledge gaps are never captured or used to improve future sessions. ## Core Features & Use Cases - Session Metrics Collection: Automatically records tool usage, requirement flow, errors, and skill/agent invocations into .git/requirements/sessions/<session_id>.json during each session. - Pattern Analysis & Recommendations: The /session-reflect command runs a session-analyzer agent that detects workflow patterns, friction points, and automation opportunities, then suggests confidence-scored updates to Serena memories, skills, and commands. - Versioned, Rollback-Capable Updates: Every applied change is recorded in .git/requirements/learning_history.json and can be undone with req learning rollback <id>. - Use Case: After a long debugging session, run /session-reflect to discover a repeated ADR lookup pattern, then approve a recommendation that creates a frequently-referenced.md memory so the next session starts with that context already available. ## Quick Start Enable session learning by setting hooks.session_learning.enabled: true in .claude/requirements.yaml, then ask Claude to run /session-reflect at the end of your session to analyze it and apply improvements.