continuous-learning-v2

Convert Claude Code session activity into confidence-weighted YAML behavioral instincts.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/xxih/ai-harness-zh --skill continuous-learning-v2-xxih
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-learning-v2
Source: https://github.com/xxih/ai-harness-zh/tree/main/references/translations/everything-claude-code/docs/zh-CN/skills/continuous-learning-v2
Command: npx skills add https://github.com/xxih/ai-harness-zh --skill continuous-learning-v2-xxih

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and operationalize repeated behaviors, corrections, and tool workflows from Claude Code sessions so that project- and global-scoped conventions are learned automatically instead of being manually re-encoded each time.

Core Features & Use Cases

  • Deterministic hook-based observation: use PreToolUse/PostToolUse hooks to capture every tool call and prompt reliably.
  • Project-scoped, confidence-weighted instincts: generate atomic YAML "instincts" with triggers, evidence, and evolving confidence scores that default to project scope and can be promoted to global.
  • Evolution and governance: cluster related instincts into skills/commands/agents, export/import patterns, and promote recurring high-confidence instincts across projects.
  • Use case: automatically detect a React hooks pattern in a repository, create a project instinct "use-react-hooks-pattern" with supporting evidence, and later evolve it into a reusable skill or promote it when observed across multiple projects.

Quick Start

Enable the observer hooks and run the background observer to analyze recent session observations and create project-scoped instincts for your current repository.

Frequently Asked Questions about continuous-learning-v2

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

FAQPage Schema
How do I capture Claude Code session activity and tool usage for analysis?

Capture Claude Code session activity and tool usage by enabling deterministic PreToolUse and PostToolUse hooks. These hooks reliably observe every tool call and prompt, providing the raw session data needed to detect repeated workflows and error-resolution patterns within git repositories.

What are behavioral instincts in Claude Code session analysis and how do they work?

Behavioral instincts are atomic YAML rules generated from session analysis that encode detected corrections, tool preferences, and repeated workflows. Each instinct includes triggers, supporting evidence, and an evolving confidence score, defaulting to project scope with metadata supporting clustering and evolution.

How do I automatically learn project conventions from Claude Code sessions instead of re-encoding them manually?

Automatically learn project conventions by running a background observer that analyzes recent session observations. It detects repeated behaviors and error-resolution patterns, then generates project-scoped, confidence-weighted YAML instincts so conventions are operationalized without manual re-encoding.

Can I promote project-scoped instincts to global scope when patterns appear across multiple repositories?

Yes, project-scoped instincts can be promoted to global scope. When high-confidence behavioral patterns are observed recurring across multiple projects, the governance mechanism supports promoting them, alongside clustering related instincts into reusable skills, commands, or agents.

Does continuous learning from session observations require a specific repository setup?

Session observation requires Claude Code sessions within git repositories to detect project-scoped patterns. The hook-based observation system captures tool calls and prompts reliably, and the generated instincts include scope metadata to distinguish between project-level and global-level conventions.

What is the best way to export and import behavioral instincts across different projects?

Export and import behavioral instincts using the built-in import/export pattern support. This allows confidence-weighted YAML instincts, including their triggers and evidence, to be transferred between projects, facilitating the evolution of recurring high-confidence patterns into reusable skills.