learned▌

Extract software engineering lessons from recent git changes by analyzing actual code patterns. \n \n Analyzes code diffs against a curated principles reference to identify dominant patterns, trade-offs, and structural decisions \n Supports multiple scopes: feature branches vs. main, specific commits, commit ranges, or uncommitted working changes \n Maps findings to concrete SE principles with specific file and line references, avoiding generic advice \n Presents lessons in a reflective format t