lesson-learned

To extract lessons from git commit history, analyze recent diffs and commit messages to identify applied principles and anti-patterns. The skill reads recent changes and maps them to named engineering principles, outputting structured takeaways with evidence references.

Mapping code refactoring changes to software engineering principles involves analyzing git diffs against an established principles reference. This skill compares your recent commits against se-principles.md and anti-patterns to surface the exact trade-offs made.

The lesson extraction analyzes the last five commits when operating on the main branch. If you are working on a feature branch, it reads the entire branch history to capture the full context of your feature work, debugging, or refactoring.

You can generate a code review summary from recent git diff changes by reading commit messages and change context. This skill processes your recent git history to produce conversation-ready, structured lessons grounded in software engineering principles.

Yes, the lesson extraction tool works with both feature branches and main branch history. It automatically detects your current git branch, analyzing the last five commits on main or the entire commit history when on a feature branch.

Reviewing anti-patterns and engineering principles after committing code surfaces actionable takeaways from your recent work. This reflection process identifies applied trade-offs and maps findings to named principles, accelerating developer growth through grounded lessons.