Extract software engineering lessons from git history and diffs.
npx skills add https://github.com/JBonfim/skill-developer --skill lesson-learned-jbonfim
Please help me install this Agent Skill. Skill: lesson-learned Source: https://github.com/JBonfim/skill-developer/tree/main/.agents/skills/lesson-learned Command: npx skills add https://github.com/JBonfim/skill-developer --skill lesson-learned-jbonfim
It turns recent code changes into concrete software engineering lessons so you can learn from what you already shipped instead of repeating the same trade-offs blindly.
Ask for an engineering takeaway after your latest PR or debugging work (for example: “What is the lesson here from these recent commits?”).
High-intent search queries and answers about installing and using this skill.
You can extract engineering lessons from git commit history by analyzing recent diffs and commit messages to identify patterns, then mapping those observations to named software principles like SOLID or DRY for actionable takeaways.
The best way to reflect on code changes after a refactor is to review the git diff and connect the specific modifications to software engineering principles. This yields 1-3 code-grounded lessons with a next step for future work.
Yes, you can analyze working tree changes or specific commit SHAs for code review takeaways. The analysis supports configurable commit ranges, specific commit SHAs, and uncommitted working-tree changes to generate reflective engineering lessons.
Git diff analysis tools map code changes to software principles by loading a curated engineering principles catalog, evaluating observed patterns in the diff against this reference, and producing specific, code-grounded takeaways mapped to principles like KISS or YAGNI.
You should generate engineering takeaways from your codebase after feature work, debugging sessions, or refactoring. Applying this reflective analysis anytime you want to learn from specific commits helps you avoid repeating the same trade-offs blindly.
k97Analyzes git diffs to generate standardized conventional commit messages.
mkalhitti-cloudEnforce mandatory lessons-learned reviews before NinjaTrader code changes.
skkeoriwExecute pre-commit code review with static analysis and automated tests.
pedronauckAnalyzes git history to extract software engineering lessons and principles.
