10x-lesson

Document recurring code review patterns into a central lessons.md file.

Updated May 18, 2026
One-click install
npx skills add https://github.com/PixelSculptor/osce-triager --skill 10x-lesson-pixelsculptor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-lesson
Source: https://github.com/PixelSculptor/osce-triager/tree/main/.claude/skills/10x-lesson
Command: npx skills add https://github.com/PixelSculptor/osce-triager --skill 10x-lesson-pixelsculptor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps document recurring rules or patterns into a centralized knowledge base, facilitating future reviews and implementations by other tools and processes.

Core Features & Use Cases

  • Rule Capture: Capture a repeating rule or pattern identified during code reviews or implementations.
  • Contextual Entry: Store the rule in context/foundation/lessons.md for easy reference by other tools during their workflows.
  • Use Case: When a class of bug or design pitfall is observed, use this skill to record the issue and its resolution in a structured format, making it available for future reference.

Quick Start

Use the /10x-lesson skill to record a lesson learned from a code review.

Frequently Asked Questions about 10x-lesson

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

FAQPage Schema
How do I document recurring code review patterns for future reference?

You can document recurring code review patterns by capturing the rule context, problem, and relevant tool categories into a centralized lessons.md file. This structured format makes the resolution available for future reference by other related tools and workflows.

What is the best way to record lessons learned from a code review?

Recording lessons learned involves capturing a repeating rule or design pitfall observed during code review and storing it in context/foundation/lessons.md. This centralizes the knowledge base for easy access by other related tools during their workflows.

How does pattern capture work for recurring design pitfalls?

Pattern capture works by requiring the input of the rule context, the specific problem, the rule itself, and relevant tool categories. It then stores these entries as structured entries in a central lessons.md file for easy access.

Can I use this knowledge base approach for implementation rules as well as code review rules?

Yes, this knowledge base approach supports capturing recurring rules identified during both code reviews and implementations. It stores the issue and its resolution in a structured format within lessons.md, facilitating future reviews and implementations.

What input is required to add a recurring rule to lessons.md?

Adding a recurring rule to lessons.md requires inputting the rule context, the problem description, the rule itself, and the relevant tool categories. This ensures the captured pattern is structured for easy access by other tools.