What problem does it solve?
Analyze developer corrections from the current coding session and persist lessons learned as rules in CLAUDE.md files or memory. Use this skill at the end of a coding session, after the developer has reviewed and corrected your work, when the developer says "self-improve", "learn from this session", "what did you learn", "update your rules", "remember this for next time", or any time the developer wants to capture feedback from corrections they made. Also trigger when the developer explicitly asks you to reflect on mistakes or extract patterns from their edits.
Core Features & Use Cases
- Extract reusable rules from corrections and persist them so future sessions benefit
- Persist rules to CLAUDE.md or memory for long-term improvement
- Run this before wrapping up a session to save improvements while context is still available
Quick Start
After a coding session where corrections are made, run self-improve to extract rules and store them for future sessions.