continuous-learning

Extract reusable patterns from Claude Code session transcripts via Stop hook.

4|1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/rongarede/skill-snapshots --skill continuous-learning-rongarede
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-learning
Source: https://github.com/rongarede/skill-snapshots/tree/main/meta/continuous-learning
Command: npx skills add https://github.com/rongarede/skill-snapshots --skill continuous-learning-rongarede

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

Automatically extracts reusable patterns from Claude Code sessions and saves them as learned skills for future use.

Core Features & Use Cases

  • End-of-session evaluation using a Stop hook to identify actionable patterns.
  • Pattern detection across transcripts (e.g., error resolutions, user corrections, debugging techniques, project-specific conventions).
  • Persists learned skills to ~/.claude/skills/learned/ for reuse in future sessions.

Quick Start

  1. Configure Claude Code to run the evaluate-session.sh script as a Stop-hook after each session.
  2. Ensure the learned skills directory exists at ~/.claude/skills/learned/ and that CLAUDE_TRANSCRIPT_PATH points to the current session transcript.
  3. Edit config.json to set min_session_length and patterns_to_detect as needed.

Frequently Asked Questions about continuous-learning

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

FAQPage Schema
How do I extract reusable patterns from Claude Code session transcripts?

You can extract reusable patterns from Claude Code session transcripts by configuring a Stop hook to run an evaluation script at the end of each session, automatically identifying error resolutions and debugging techniques to save as learned skills.

What is continuous learning in Claude Code and how does it work?

Continuous learning automates pattern detection by evaluating your session transcript via CLAUDE_TRANSCRIPT_PATH when a session ends, extracting project-specific conventions and saving them as reusable skills to a configured directory.

Do I need jq to detect learned skills from my Claude Code sessions?

Yes, you need jq installed as a dependency to parse the session transcript and extract learned skills from your Claude Code sessions, alongside setting up a Stop hook and configuring your learned-skills path.

How do I configure a Stop hook to save error resolutions from Claude Code?

To configure a Stop hook for saving error resolutions, point it to the evaluate-session.sh script, ensure CLAUDE_TRANSCRIPT_PATH is set, and edit config.json to specify the minimum session length and patterns to detect.

What types of debugging techniques can be saved as learned skills from session transcripts?

The pattern detection mechanism saves debugging techniques, error resolutions, user corrections, and project-specific conventions from session transcripts, storing them as learned skills in your configured ~/.claude/skills/learned/ directory.

Can I set a minimum session length for evaluating Claude Code transcripts?

Yes, you can set a minimum session length for transcript evaluation by editing the config.json file, ensuring that only sufficiently long Claude Code sessions are processed for pattern detection and skill extraction.