lesson-learned
Audited by Runlayer on Feb 21, 2026
Malicious tool definition detected
Tool: README.md Description: # Lesson Learned Extract software engineering takeaways from your recent code changes. ## Purpose Most developers ship code and move on.
Malicious tool definition detected
Tool: SKILL.md Description: --- name: lesson-learned description: "Analyze recent code changes via git history and extract software engineering lessons. Use when the user asks 'what is the lesson here?', 'what can I learn from this?', 'engineering takeaway', 'what did I just learn?', 'reflect on this code', or wants to extract principles from recent work." --- # Lesson Learned Extract specific, grounded software engineering lessons from actual code changes.
Malicious tool definition detected
Tool: references/anti-patterns.md Description: --- description: Common anti-patterns to detect in code diffs. Use alongside se-principles.md for balanced analysis -- principles show what's good, anti-patterns show what to watch for.
Malicious tool definition detected
Tool: references/se-principles.md Description: --- description: Curated catalog of software engineering principles. Load this before analyzing code changes so you can map observations to named principles. --- # Software Engineering Principles Use this as a lookup table. When you spot a pattern in a diff, find the matching principle here. Each entry includes **code signals** -- what to look for in actual changes. ## Design Principles (SOLID) **Single Responsibility Principle (SRP)** A module shou