self-improvement

To log development errors across sessions, this skill captures corrections and failures into dedicated markdown files like ERRORS.md and LEARNINGS.md. It automatically organizes recurring patterns to enable continuous improvement in your workflows.

Continuous improvement logging is the process of capturing learnings, errors, and corrections during development tasks to prevent recurring mistakes across sessions. This mechanism stores entries in structured markdown files to track agent progress over time.

Yes, you can promote captured learnings by extracting reusable insights to CLAUDE.md, AGENTS.md, or .github/copilot-instructions.md. This elevates valuable entries into permanent agent configuration files for broader application.

Yes, OpenClaw supports cross-session sharing by integrating hooks that automate prompts and share logged learnings across different environments. This ensures improvements persist beyond a single task or session.

You need to log a learning entry after a task completes, specifically following failures, user corrections, or when identifying missing capabilities. This captures actionable context while the development workflow is still fresh.

The best way to track recurring errors across multiple agents is to centralize logs in structured files like ERRORS.md and LEARNINGS.md. This approach captures patterns uniformly and integrates with OpenClaw for cross-agent visibility.