continuous-learning

Extract reusable patterns from opencode sessions into learned skills.

3|1|Updated Jan 24, 2026

Search Tags:#automation #learning #patterns #sessions #opencode #pattern-detection

Ready to run

npx skills add https://github.com/monch1962/everything-opencode --skill continuous-learning-monch1962

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: continuous-learning
Source: https://github.com/monch1962/everything-opencode/tree/main/skills/continuous-learning
Command: npx skills add https://github.com/monch1962/everything-opencode --skill continuous-learning-monch1962

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automatically evaluates opencode sessions at the end to extract reusable patterns and save them as learned skills for future use.

Core Features & Use Cases

Stop-hook at session end: Automatically analyzes the transcript once a session concludes.
Pattern detection: Identifies reusable patterns such as error_resolution, user_corrections, workarounds, debugging_techniques, and project_specific.
Skill extraction & persistence: Saves discovered patterns to ~/.opencode/skills/learned/.
Configurable behavior: Governed by config.json fields like min_session_length, extraction_threshold, auto_approve, learned_skills_path, patterns_to_detect, and ignore_patterns.

Quick Start

Run a sample opencode session with at least 10 messages and inspect the learned skills created at ~/.opencode/skills/learned/.

Frequently Asked Questions about continuous-learning

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

FAQPage Schema

How can I automatically extract reusable patterns from my opencode sessions?▼

Pattern extraction happens automatically at session end when your session meets the configured minimum length. The Skill detects error_resolution, user_corrections, workarounds, debugging_techniques, and project_specific patterns, then saves them to ~/.opencode/skills/learned/ for reuse in future sessions.

What patterns does this Skill detect and learn from sessions?▼

The Skill identifies five pattern types: error_resolution (how you fix errors), user_corrections (manual fixes you apply), workarounds (alternative solutions), debugging_techniques (approaches to troubleshooting), and project_specific (context-dependent methods). Which patterns to detect is configurable via patterns_to_detect in config.json.

How do I configure when and what patterns get learned automatically?▼

Configure behavior in config.json with fields like min_session_length (minimum session size to trigger extraction), extraction_threshold (confidence level for pattern detection), auto_approve (whether to save patterns without review), and ignore_patterns (patterns to exclude). The Stop hook runs evaluation automatically at session end.

Where are learned patterns stored and how do I access them?▼

Learned patterns are saved to ~/.opencode/skills/learned/ by default, though you can customize the path with learned_skills_path in config.json. Once stored, these patterns become reusable skills available for future opencode sessions.

Do I need to set up anything before this Skill can learn patterns?▼

Yes—configure a Stop hook in ~/.opencode/settings.json to trigger pattern evaluation at session end. The Skill also requires config.json with settings like min_session_length and patterns_to_detect. Run a sample session with at least 10 messages to see learned skills created.

What's the difference between auto_approve enabled and disabled for learned patterns?▼

With auto_approve enabled, detected patterns save automatically to ~/.opencode/skills/learned/ without review. Disabled requires manual approval before patterns persist, giving you control over which learned skills become active for future sessions.