lesson-learned
Skill0 starsChanged 4 months agoMITView on GitHub
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.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- compozy/compozytheir own version, first seen Nov 13, 2026
- mementomori-co/maker-masterytheir own version, first seen Oct 25, 2026
- sueryue/Claude-Skilllsword for word, first seen Jul 28, 2026
- nbirkner/digital-brainword for word, first seen Apr 12, 2026
- FelipeAngeli/skillsword for word, first seen Apr 10, 2026
- pedronauck/skillsword for word, first seen Apr 3, 2026
Other versions6 projects use a version of this.
Word for word · 4
- pedronauck/skills★ 655100% same
- FelipeAngeli/skills★ 2100% same
- nbirkner/digital-brain★ 0100% same
- sueryue/Claude-Skillls★ 0100% same
Edited · 0
None found.
Wrote their own version · 2
- compozy/compozy★ 2.9ksame name
- mementomori-co/maker-mastery★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository121 other files it gives its agents.
- agent-md-refactorSkill
- backend-to-frontend-handoff-docsSkill
- c4-architectureSkill
- codexSkill
- command-creatorSkill
- commit-workSkill
- crafting-effective-readmesSkill
- daily-meeting-updateSkill
- database-schema-designerSkill
- datadog-cliSkill
- dependency-updaterSkill
- agency-brand-guardianSkill
- design-system-starterSkill
- agency-ui-designerSkill
- agency-ux-researcherSkill
- difficult-workplace-conversationsSkill
- domain-name-brainstormerSkill
- draw-ioSkill
- agency-ai-data-remediation-engineerSkill
- agency-ai-engineerSkill
- agency-api-platform-engineerSkill
- agency-autonomous-optimization-architectSkill
- agency-backend-architectSkill
- agency-cms-developerSkill
- agency-codebase-onboarding-engineerSkill
- agency-code-reviewerSkill
- agency-database-optimizerSkill
- agency-database-reliability-engineerSkill
- agency-data-engineerSkill
- agency-data-visualization-engineerSkill
- agency-desktop-app-engineerSkill
- agency-devops-automatorSkill
- agency-drupal-performance-engineerSkill
- agency-drupal-shopping-cart-engineerSkill
- agency-email-intelligence-engineerSkill
- agency-embedded-firmware-engineerSkill
- agency-feishu-integration-developerSkill
- agency-filament-optimization-specialistSkill
- agency-finops-engineerSkill
- agency-frontend-developerSkill
- agency-gaussdb-expert-engineerSkill
- agency-git-workflow-masterSkill
- agency-internationalization-engineerSkill
- agency-identity-access-engineerSkill
- agency-incident-response-commanderSkill
- agency-iot-fleet-engineerSkill
- agency-it-service-managerSkill
- agency-llm-post-training-engineerSkill
- agency-minimal-change-engineerSkill
- agency-mobile-app-builderSkill
- agency-mobile-release-engineerSkill
- agency-multi-agent-systems-architectSkill
- agency-network-engineerSkill
- agency-orgscript-engineerSkill
- agency-payments-billing-engineerSkill
- agency-privacy-engineerSkill
- agency-prompt-engineerSkill
- agency-rag-pipeline-engineerSkill
- agency-rapid-prototyperSkill
- agency-realtime-collaboration-engineerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read references/se-principles.md to have the principle catalog available
- Distinctive: line 22
Ask the user or infer from context what to analyze.
- Distinctive: line 32
If on a feature branch: analyze branch commits vs main
- Distinctive: line 33
If on main: analyze the last 5 commits
- Distinctive: line 34
If the user provides a different scope, use that
- Distinctive: line 38
Run git log with the determined scope to get the commit list and messages
- Distinctive: line 39
Run git diff for the full diff of the scope
- Distinctive: line 40
If the diff is large (>500 lines), use git diff --stat first, then selectively read the top 3-5 most-changed files
- Distinctive: line 42
Only read changed files. Do not read the entire repo.
- Distinctive: line 76
If there is a second lesson worth noting (maximum 2 additional):
- Distinctive: line 101
Reflective, not prescriptive: Use the user's own code as primary evidence.
- Distinctive: line 103
If the code is good, say so: Not every lesson is about what went wrong.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lesson Learned
Extract specific, grounded software engineering lessons from actual code changes. Not a lecture -- a mirror. Show the user what their code already demonstrates.
Before You Begin
Load the principles reference first.
- Read
references/se-principles.mdto have the principle catalog available - Optionally read
references/anti-patterns.mdif you suspect the changes include areas for improvement - Determine the scope of analysis (see Phase 1)
Do not proceed until you've loaded at least se-principles.md.
Phase 1: Determine Scope
Ask the user or infer from context what to analyze.
| Scope | Git Commands | When to Use |
| Feature branch | git log main..HEAD --oneline + git diff main...HEAD | User is on a non-main branch (default) |
| Last N commits | git log --oneline -N + git diff HEAD~N..HEAD | User specifies a range, or on main (default N=5) |
| Specific commit | git show <sha> | User references a specific commit |
| Working changes | git diff + git diff --cached | User says "what about these changes?" before committing |
Default behavior:
- If on a feature branch: analyze branch commits vs main
- If on main: analyze the last 5 commits
- If the user provides a different scope, use that
Phase 2: Gather Changes
- Run
git logwith the determined scope to get the commit list and messages - Run
git difffor the full diff of the scope - If the diff is large (>500 lines), use
git diff --statfirst, then selectively read the top 3-5 most-changed files - Read commit messages carefully -- they contain intent that raw diffs miss
- Only read changed files. Do not read the entire repo.
Phase 3: Analyze
Identify the dominant pattern -- the single most instructive thing about these changes.
Look for:
- Structural decisions -- How was the code organized? Why those boundaries?
- Trade-offs made -- What was gained vs. sacrificed? (readability vs. performance, DRY vs. clarity, speed vs. correctness)
- Problems solved -- What was the before/after? What made the "after" better?
- Missed opportunities -- Where could the code improve? (present gently as "next time, consider...")
Map findings to specific principles from references/se-principles.md. Be specific -- quote actual code, reference actual file names and line changes.
Phase 4: Present the Lesson
Use this template:
## Lesson: [Principle Name]
**What happened in the code:**
[2-3 sentences describing the specific change, referencing files and commits]
**The principle at work:**
[1-2 sentences explaining the SE principle]
**Why it matters:**
[1-2 sentences on the practical consequence -- what would go wrong without this, or what goes right because of it]
**Takeaway for next time:**
[One concrete, actionable sentence the user can apply to future work]If there is a second lesson worth noting (maximum 2 additional):
---
### Also worth noting: [Principle Name]
**In the code:** [1 sentence]
**The principle:** [1 sentence]
**Takeaway:** [1 sentence]What NOT to Do
| Avoid | Why | Instead |
| Listing every principle that vaguely applies | Overwhelming and generic | Pick the 1-2 most relevant |
| Analyzing files that were not changed | Scope creep | Stick to the diff |
| Ignoring commit messages | They contain intent that diffs miss | Read them as primary context |
| Abstract advice disconnected from the code | Not actionable | Always reference specific files/lines |
| Negative-only feedback | Demoralizing | Lead with what works, then suggest improvements |
| More than 3 lessons | Dilutes the insight | One well-grounded lesson beats seven vague ones |
Conversation Style
- Reflective, not prescriptive. Use the user's own code as primary evidence.
- Never say "you should have..." -- instead use "the approach here shows..." or "next time you face this, consider..."
- If the code is good, say so. Not every lesson is about what went wrong. Recognizing good patterns reinforces them.
- If the changes are trivial (a single config tweak, a typo fix), say so honestly rather than forcing a lesson. "These changes are straightforward -- no deep lesson here, just good housekeeping."
- Be specific. Generic advice is worthless. Every claim must point to a concrete code change.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

