continuous-learning
Skill1 starsChanged 9 months agoMITView on GitHub
Automatically extract reusable patterns from Claude Code sessions and save them as learned skills for future use.
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 55
Add to your ~/.claude/settings.json:
“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Continuous Learning Skill
Automatically evaluates Claude Code sessions on end to extract reusable patterns that can be saved as learned skills.
How It Works
This skill runs as a Stop hook at the end of each session:
- Session Evaluation: Checks if session has enough messages (default: 10+)
- Pattern Detection: Identifies extractable patterns from the session
- Skill Extraction: Saves useful patterns to
~/.claude/skills/learned/
Configuration
Edit config.json to customize:
{
"min_session_length": 10,
"extraction_threshold": "medium",
"auto_approve": false,
"learned_skills_path": "~/.claude/skills/learned/",
"patterns_to_detect": [
"error_resolution",
"user_corrections",
"workarounds",
"debugging_techniques",
"project_specific"
],
"ignore_patterns": [
"simple_typos",
"one_time_fixes",
"external_api_issues"
]
}Pattern Types
| Pattern | Description |
error_resolution | How specific errors were resolved |
user_corrections | Patterns from user corrections |
workarounds | Solutions to framework/library quirks |
debugging_techniques | Effective debugging approaches |
project_specific | Project-specific conventions |
Hook Setup
Add to your ~/.claude/settings.json:
{
"hooks": {
"Stop": [{
"matcher": "*",
"hooks": [{
"type": "command",
"command": "~/.claude/skills/continuous-learning/evaluate-session.sh"
}]
}]
}
}Why Stop Hook?
- Lightweight: Runs once at session end
- Non-blocking: Doesn't add latency to every message
- Complete context: Has access to full session transcript
Related
- The Longform Guide - Section on continuous learning
/learncommand - Manual pattern extraction mid-session
Comparison Notes (Research: Jan 2025)
vs Homunculus (github.com/humanplane/homunculus)
Homunculus v2 takes a more sophisticated approach:
| Feature | Our Approach | Homunculus v2 |
| Observation | Stop hook (end of session) | PreToolUse/PostToolUse hooks (100% reliable) |
| Analysis | Main context | Background agent (Haiku) |
| Granularity | Full skills | Atomic "instincts" |
| Confidence | None | 0.3-0.9 weighted |
| Evolution | Direct to skill | Instincts → cluster → skill/command/agent |
| Sharing | None | Export/import instincts |
Key insight from homunculus:
"v1 relied on skills to observe. Skills are probabilistic—they fire ~50-80% of the time. v2 uses hooks for observation (100% reliable) and instincts as the atomic unit of learned behavior."
Potential v2 Enhancements
- Instinct-based learning - Smaller, atomic behaviors with confidence scoring
- Background observer - Haiku agent analyzing in parallel
- Confidence decay - Instincts lose confidence if contradicted
- Domain tagging - code-style, testing, git, debugging, etc.
- Evolution path - Cluster related instincts into skills/commands
See: /Users/affoon/Documents/tasks/12-continuous-learning-v2.md for full spec.
Other versions39 projects use a version of this.
Word for word · 3
- zkw15555506767-boop/claude-skills★ 1100% same
- EvanZzhang/claude-configs★ 0100% same
- Samueladewole/claude-skills★ 0100% same
Edited · 20
- loulanyue/awesome-claude-notes★ 27285% same
- Fmarzochi/EGC★ 6155% same
- xfstudio/skills★ 9100% same
- Lukasbrujula/claude-code-framework★ 485% same
- XD3an/cc-plus★ 4100% same
- get-proofpilot/claude-skills-catalog★ 185% same
- junimnjw/everything-claude-code★ 185% same
- royaluniondesign-sys/claude-os★ 187% same
- tarrragon/claude-skills★ 116% same
- TironFox/everything-claude-code★ 185% same
10 more not listed
Wrote their own version · 16
- blader/claude-code-continuous-learning-skill★ 2.4ksame name
- blader/Claudeception★ 2.4ksame name
- MRCalderon3D/everything-game-dev-code★ 91same name
- AlexMikhalev/claude-code-continuous-learning-skill★ 36same name
- vneseyoungster/ChocoVine★ 27same name
- mhylle/claude-skills-collection★ 20same name
- ckorhonen/claude-skills★ 17same name
- darknecrocities/SkillBuilder★ 13same name
- ShaheerKhawaja/ProductionOS★ 8same name
- peopleforrester/claude-dotfiles★ 3same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- rules/agents.mdAGENTS.md
- examples/CLAUDE.mdCLAUDE.md
- backend-patternsSkill
- clickhouse-ioSkill
- codemap-templateSkill
- coding-standardsSkill
- continuous-learning-v2Skill
- django-patternsSkill
- django-securitySkill
- django-trophySkill
- django-verificationSkill
- eval-harnessSkill
- frontend-patternsSkill
- golang-patternsSkill
- golang-testingSkill
- iterative-retrievalSkill
- java-coding-standardsSkill
- jpa-patternsSkill
- postgres-patternsSkill
- progress-documentationSkill
- project-guidelines-exampleSkill
- python-patternsSkill
- python-testingSkill
- security-reviewSkill
- springboot-patternsSkill
- springboot-securitySkill
- springboot-trophySkill
- springboot-verificationSkill
- strategic-compactSkill
- trophy-workflowSkill
- verification-loopSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

