Self-Improving Skills in Claude Code

Quick Overview

The video demonstrates a self-improving skills system for Claude Code where user corrections during a session are extracted via a /reflect command, reviewed, and then automatically committed and pushed to GitHub, creating a permanent feedback loop that makes the skill smarter over time without requiring manual session restarts.

Key Points: The core problem addressed is that standard LLMs do not learn from user corrections across separate sessions, forcing users to repeat instructions (00:04). The solution involves a /reflect command which analyzes the current session, extracts corrections (signals) and approvals (confirmations), and proposes skill updates (01:35, 03:06). The manual flow requires the user to run /reflect after a session, which references the skill file (e.g., //.claude/skills/code-review/SKILL.md) to update it (02:15, 03:10). The automatic flow uses a 'Stop Hook' configured in /.claude/settings.json to trigger the /reflect skill script automatically when Claude stops responding (04:56, 05:28). The /reflect skill analyzes the conversation for corrections (High/Medium confidence) and success patterns, then proposes Git changes including a commit message (03:26, 04:14). If approved, Claude executes edits to the skill file, runs git add/commit, and pushes to origin/main, ensuring the next session uses the improved skill (04:33, 04:42). The benefits include seeing skill evolution over time, easy rollback of bad changes via Git history, synchronization across machines, and sharing improvements (06:57).

Context: This video explains a system implemented in Claude Code designed to enable Large Language Models (LLMs) to continuously improve their specialized 'skills' based on direct user feedback during coding sessions. The primary challenge addressed is the stateless nature of current LLM interactions, where corrections made in one session are forgotten in the next. The proposed solution centers around a '/reflect' mechanism that captures user feedback (corrections and confirmations) and integrates these learned patterns directly back into the skill's configuration file using Git version control.

Raw markdown version of this recap