What documentation does this skill require to function?

It relies on a principles reference, typically 'references/se-principles.md', to provide a catalog of engineering standards to compare your code against.

Does it read the entire codebase for every analysis?

No, it is optimized for efficiency and scope. It only reads changed files and commit messages to ensure the analysis remains relevant to the specific changes you are reflecting on.

How does the Lesson Learned skill analyze my code?

The skill examines your git log and diffs within a specific scope—such as a feature branch or the last five commits—to identify structural patterns and map them to engineering principles.

Is the feedback critical or prescriptive?

The feedback is designed to be reflective and grounded. It focuses on showing you what your code already demonstrates, using a 'mirror' approach rather than a 'lecturer' approach.

Can it identify mistakes or anti-patterns in my work?

Yes, if 'references/anti-patterns.md' is available, the skill can identify areas for improvement and present them as constructive 'next time' takeaways.

Software Engineering Lessons

Name: Software Engineering Lessons
Author: softaworks

bysoftaworks

•

713

•

Learning & Documentation

Extracts actionable software engineering principles and reflections from recent git history and code changes.

This skill transforms raw code changes into meaningful learning opportunities by analyzing git logs and diffs against established software engineering principles. By acting as a reflective mirror rather than a lecturer, it identifies structural decisions, architectural trade-offs, and patterns in your work, providing specific, grounded takeaways that help developers internalize best practices through their own implementation history.

Key Features

01Structured, actionable takeaways linked directly to specific file lines and logic for concrete learning.

02713 GitHub stars

03Automated git history and diff analysis across feature branches, specific commits, or working changes.

04Identification of architectural trade-offs such as readability vs. performance and DRY vs. clarity.

05Intent-aware analysis that incorporates commit messages to understand the 'why' behind the code.

06Mapping of code changes to established software engineering principles and documented anti-patterns.

Use Cases

01Generating educational summaries of complex technical changes for team knowledge sharing and documentation.

02Reflecting on a completed feature branch to extract engineering principles before a merge request.

03Conducting a self-guided code review to identify recurring patterns or missed architectural opportunities.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add softaworks/agent-toolkit lesson-learned

For use in Claude.ai and ChatGPT

Download Skill