A two-stage system that helps Claude Code learn from user corrections.
Stage 1: Capture (Automatic)
Hooks detect correction patterns ("no, use X", "actually...", "use X not Y") and queue them to ~/.claude/learnings-queue.json.
Stage 2: Process (Manual)
User runs /reflect to review and apply queued learnings to CLAUDE.md files.
| Command | Purpose |
|---|---|
/reflect |
Process queued learnings with human review |
/reflect --scan-history |
Scan past sessions for missed learnings |
/reflect --dry-run |
Preview changes without applying |
/skip-reflect |
Discard all queued learnings |
/view-queue |
View pending learnings without processing |
Remind users about /reflect when:
High-confidence corrections:
~/.claude/CLAUDE.md - Global learnings (model names, general patterns)./CLAUDE.md - Project-specific learnings (conventions, tools, structure)User: no, use gpt-5.1 not gpt-5 for reasoning tasks
Claude: Got it, I'll use gpt-5.1 for reasoning tasks.
[Hook captures this correction to queue]
User: /reflect
Claude: Found 1 learning queued. "Use gpt-5.1 for reasoning tasks"
Scope: global
Apply to ~/.claude/CLAUDE.md? [y/n]
Execute self-learning system that captures corrections during sessions and syncs them to CLAUDE.
| Error | Cause | Resolution |
|---|---|---|
| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with Claude Reflect |
| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
Basic usage: Apply claude reflect to a standard project setup with default configuration options.
Advanced scenario: Customize claude reflect for production environments with multiple constraints and team-specific requirements.