continuous-learning

Extract reusable problem-solving patterns from Claude Code session transcripts.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill continuous-learning-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-learning
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/skills/continuous-learning
Command: npx skills add https://github.com/luongldptit/move-ticket --skill continuous-learning-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq.

What problem does it solve?

Manually identifying and saving useful workflows, debugging techniques, and project-specific patterns from Claude Code sessions is time-consuming, and valuable knowledge is often lost after sessions end. This skill solves that by automatically extracting reusable patterns from your session history.

Core Features & Use Cases

  • Automatic Stop Hook Execution: Runs once at the end of each Claude Code session to evaluate for extractable patterns without adding latency to your in-session interactions.
  • Customizable Pattern Filtering: Lets you adjust configuration to target specific pattern types (like error resolutions, workarounds, debugging techniques) and ignore irrelevant ones (like simple typos, one-time fixes).
  • Centralized Pattern Library: Saves approved extracted patterns to a dedicated local directory for easy reuse across future projects and sessions. For example, if you repeatedly resolve the same framework build error, this skill will capture that resolution so you can apply it instantly in future sessions.

Quick Start

Activate the continuous-learning skill and configure your Claude Code Stop hook to automatically save reusable problem-solving patterns from your sessions to your local learned skills library.

Frequently Asked Questions about continuous-learning

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

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

You can automatically extract reusable patterns from Claude Code session transcripts by configuring a Stop hook to evaluate your session history and save debugging techniques to a local learned skills directory. This runs at the end of each session without adding latency.

How does a Stop hook capture debugging workflows when a Claude Code session ends?

A Stop hook captures debugging workflows by executing once at the end of a Claude Code session to evaluate the transcript for extractable error resolutions and project-specific conventions. Approved patterns are then saved locally for reuse.

Can I filter which error resolutions and workarounds get saved from my Claude Code sessions?

Yes, you can filter which error resolutions and workarounds get saved by adjusting custom configuration settings for pattern detection thresholds. This allows you to target specific debugging techniques while ignoring irrelevant patterns like simple typos or one-time fixes.

Do I need jq to use continuous-learning for saving session patterns?

Yes, you need jq installed as a dependency to use continuous-learning for saving session patterns. You also need a configured Stop hook in Claude Code settings and a local directory to store the extracted learned skills.

What is the best way to prevent losing workflow knowledge after Claude Code sessions end?

The best way to prevent losing workflow knowledge after Claude Code sessions end is to automate pattern extraction with a Stop hook. This captures your debugging techniques and project-specific conventions into a centralized library for future reuse.

When should I not use automated pattern extraction on my Claude Code session history?

You should not use automated pattern extraction on your Claude Code session history if your work consists mainly of simple typos or one-time fixes. The skill is designed for capturing reusable debugging techniques and recurring project-specific conventions.