continuous-learning

Extracts reusable patterns from Claude Code sessions and saves them as learned skills.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill continuous-learning-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-learning
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/continuous-learning
Command: npx skills add https://github.com/ibytechaos/claude --skill continuous-learning-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq.

What problem does it solve? Valuable problem-solving patterns discovered during Claude Code sessions are lost when the session ends, forcing users to rediscover the same fixes repeatedly. ## Core Features & Use Cases - Automatic Session Evaluation: Runs as a Stop hook at session end to detect extractable patterns without adding per-message latency. - Configurable Pattern Detection: Detects error resolutions, user corrections, workarounds, debugging techniques, and project-specific conventions via config.json thresholds. - Learned Skill Persistence: Saves extracted patterns to ~/.claude/skills/learned/ for reuse in future sessions. - Use Case: After a long debugging session where you resolved a tricky framework quirk, the Stop hook flags the session for pattern extraction so the workaround becomes a reusable learned skill. ## Quick Start Add the evaluate-session.sh script as a Stop hook in ~/.claude/settings.json and adjust config.json thresholds to start capturing reusable patterns from your sessions.

Frequently Asked Questions about continuous-learning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up automatic pattern extraction from Claude Code sessions?

Add a Stop hook to ~/.claude/settings.json that runs the evaluate-session.sh script with matcher "*". The hook fires once at session end and signals whether the session contains extractable patterns.

What patterns does continuous learning detect in sessions?

It detects error resolutions, user corrections, workarounds for framework quirks, debugging techniques, and project-specific conventions. Simple typos, one-time fixes, and external API issues are ignored by default.

Why use a Stop hook instead of UserPromptSubmit for session evaluation?

The Stop hook runs once at session end, making it lightweight and non-blocking, while UserPromptSubmit runs on every message and adds latency. The Stop hook also has access to the complete session transcript.

Does the session evaluator work without jq installed?

Yes, the script falls back to default values (minimum 10 messages, default learned skills path) if jq is not installed. It prints a warning to stderr but continues running normally.

Why are short sessions skipped during pattern extraction?

Sessions below the minimum message count (default 10) rarely contain enough context to identify meaningful reusable patterns. You can lower min_session_length in config.json if you want shorter sessions evaluated.