lesson-learned — Claude Code plugin: extract principles from git history
lesson-learned scans recent git commits to surface software engineering principles and lessons from your code changes. Helps you reflect on why you built what you built.
MIT ★ 2,707 updated 2026-03-05
/plugin marketplace add softaworks/agent-toolkit
/plugin install lesson-learned@agent-toolkitWhat lesson-learned does
When you want to step back and understand your work, this plugin examines recent commits and draws out the engineering lessons hidden in the diffs. Ask it what your latest changes reveal about design patterns, quality decisions, or architectural principles — and it reflects those insights back to you.
It uses the skills/lesson-learned skill to parse commit history, spot patterns in what you changed and why, and frame them as actionable principles. Useful for solo reflection, code review discussions, or retrospectives where you want to articulate what your recent work taught you.
What it helps with
- understand the reasoning behind your recent code changes
- extract design patterns and principles from your git history
- prepare insights for retrospectives or team reviews
- turn commits into documented lessons or rules
Example prompts for the agent
- What lesson can I draw from my changes to this file?
- Analyze my git history and tell me which design principles I applied
- What does this diff reveal about code quality or architecture decisions?
How to install lesson-learned
Plugin marketplace
/plugin marketplace add softaworks/agent-toolkit/plugin install lesson-learned@agent-toolkitStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about lesson-learned
How do I install lesson-learned in Claude Code?
Run these two commands in order: /plugin marketplace add softaworks/agent-toolkit, then /plugin install lesson-learned@agent-toolkit.
What does lesson-learned do?
It reads your recent git commits, analyzes what changed, and extracts the software engineering principles behind those changes — why they matter and what they teach you about building code.
How do I use it to reflect on my code?
Ask directly: for example, 'what lesson do my last few commits teach?' or 'analyze my recent work and tell me which design patterns I applied.' The plugin walks through the git history and gives you the answer.
Source text
lesson-learned · MIT
Analyze recent code changes via git history and extract software engineering lessons. Use when reflecting on work or asking 'what is the lesson here?' Skills: skills/lesson-learned
© softaworks · MIT · softaworks/agent-toolkit