Self-Improvement Learning Log

Problem

Coding agents can repeat the same mistakes across long tasks: a failed command leaves no context, a user corrects an approach, and the next session still follows the old assumption. test-etst-test-tes turns these moments into searchable Markdown logs instead of relying on session memory.

How It Works

The skill operates around a .learnings/ directory. When an agent hits an error, correction, knowledge gap, or feature request, it writes to ERRORS.md, LEARNINGS.md, or FEATURE_REQUESTS.md, using IDs like LRN-YYYYMMDD-XXX. The core loop includes:
- Capture triggers: non-zero exit codes, exceptions, “it should be like this” corrections, or API behavior that conflicts with docs.
- State updates: entries move from pending to in_progress, resolved, wont_fix, or promoted.
- Memory promotion: rules that apply across files, prevent repeats, or encode project conventions are distilled into CLAUDE.md, AGENTS.md, .github/copilot-instructions.md, or OpenClaw files such as SOUL.md and TOOLS.md.
- Recurring patterns: similar issues are linked with See Also, prioritized when repeated, and can ingest simplify-and-harden candidate patterns.

Boundaries

It does not auto-fix code or decide which rules enter the repository; value depends on timely logging and periodic review. Teams should choose whether .learnings/ is tracked for shared use or kept local with .gitignore.