/learn - Extract Reusable Patterns
Analyze the current session and extract any patterns worth saving as skills.
Trigger
Run /learn at any point during a session when you've solved a non-trivial problem.
What to Extract
Look for:
- Error Resolution Patterns
- Debugging Techniques
- Workarounds
- Project-Specific Patterns
Output Format
Create a skill file at ~/.claude/skills/learned/[pattern-name].md:
# [Descriptive Pattern Name]Extracted: [Date]
Context: [Brief description of when this applies]
Problem
[What problem this solves - be specific]Solution
[The pattern/technique/workaround]Example
[Code example if applicable]When to Use
[Trigger conditions - what should activate this skill]
Process
- Review the session for extractable patterns
- Identify the most valuable/reusable insight
- Draft the skill file
- Ask user to confirm before saving
- Save to
~/.claude/skills/learned/
Notes
- Don't extract trivial fixes (typos, simple syntax errors)
- Don't extract one-time issues (specific API outages, etc.)
- Focus on patterns that will save time in future sessions
- Keep skills focused - one pattern per skill