lessons

Mine git history and project documentation to generate structured lesson markdown files.

Updated May 14, 2026
One-click install
npx skills add https://github.com/bonjohen/claude-local --skill lessons-bonjohen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lessons
Source: https://github.com/bonjohen/claude-local/tree/main/bundle/skills/lessons
Command: npx skills add https://github.com/bonjohen/claude-local --skill lessons-bonjohen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you discover and maintain lessons-learned documents so developers can reuse proven patterns and avoid repeated mistakes across unrelated projects.

Core Features & Use Cases

  • Discover lesson candidates by scanning git history and existing design/plan/review documents to surface reusable topics.
  • Author fully structured lessons for a chosen topic, using a consistent template and updating the lessons index.
  • Audit lesson coverage and completeness to identify gaps in structure and evidence.
  • Repair missing or thin sections (optionally scoped by file, glob, or section) while preserving existing content.

Quick Start

Run lessons in discover mode to scan for new lesson candidates without writing any files, then choose which topics you want to author.

Frequently Asked Questions about lessons

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract lessons learned from git history and project documentation?

You can extract lessons learned by mining git history and scanning existing design, plan, and review documents to surface reusable topics and patterns. This process identifies past decisions and mistakes without writing any files initially. The discover mode scans commit logs and project documentation to surface candidate topics for reusable lessons without writing any files initially.

How do I generate structured lessons-learned documents from past project mistakes?

Generate structured lessons-learned documents by authoring discovered topics into template-compliant markdown files. This creates structured entries stored under docs/lessons/ and automatically maintains an indexed README for cross-project knowledge reuse.

Can I audit and repair missing sections in existing lesson markdown files?

Yes, you can audit lesson coverage to identify gaps in structure and evidence, then repair missing or thin sections. Repairs can be scoped by file, glob, or section while preserving existing content.

Does updating lessons learned documentation overwrite existing markdown content?

No, updating lessons learned documentation applies deterministic updates that preserve existing content. It maintains an indexed README and supports adding new template-compliant entries without deleting or rewriting previous files.

What is the best way to maintain a cross-project collection of lessons learned?

The best way to maintain a cross-project collection is to store template-compliant lesson entries under docs/lessons/ with an indexed README. Regularly audit coverage and repair thin sections to ensure knowledge reuse across unrelated projects.