mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-01-31 19:53:07 +08:00
Fixes #113 The instinct commands referenced hardcoded paths that only work with manual installation (~/.claude/skills/...). When installed as a plugin, files are at ~/.claude/plugins/cache/.../skills/... Changes: - Updated instinct-status, instinct-import, evolve commands to use ${CLAUDE_PLUGIN_ROOT} with fallback to manual path - Updated observe.sh hook documentation with both install methods - Updated SKILL.md with plugin vs manual installation instructions - Removed duplicate commands from skills/continuous-learning-v2/commands/ (already exist in commands/) Users should use ${CLAUDE_PLUGIN_ROOT} in their hooks config when installed as a plugin.
4.9 KiB
4.9 KiB
name, description, command
| name | description | command |
|---|---|---|
| evolve | Cluster related instincts into skills, commands, or agents | true |
Evolve Command
Implementation
Run the instinct CLI using the plugin root path:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" evolve [--generate]
Or if CLAUDE_PLUGIN_ROOT is not set (manual installation):
python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py evolve [--generate]
Analyzes instincts and clusters related ones into higher-level structures:
- Commands: When instincts describe user-invoked actions
- Skills: When instincts describe auto-triggered behaviors
- Agents: When instincts describe complex, multi-step processes
Usage
/evolve # Analyze all instincts and suggest evolutions
/evolve --domain testing # Only evolve instincts in testing domain
/evolve --dry-run # Show what would be created without creating
/evolve --threshold 5 # Require 5+ related instincts to cluster
Evolution Rules
→ Command (User-Invoked)
When instincts describe actions a user would explicitly request:
- Multiple instincts about "when user asks to..."
- Instincts with triggers like "when creating a new X"
- Instincts that follow a repeatable sequence
Example:
new-table-step1: "when adding a database table, create migration"new-table-step2: "when adding a database table, update schema"new-table-step3: "when adding a database table, regenerate types"
→ Creates: /new-table command
→ Skill (Auto-Triggered)
When instincts describe behaviors that should happen automatically:
- Pattern-matching triggers
- Error handling responses
- Code style enforcement
Example:
prefer-functional: "when writing functions, prefer functional style"use-immutable: "when modifying state, use immutable patterns"avoid-classes: "when designing modules, avoid class-based design"
→ Creates: functional-patterns skill
→ Agent (Needs Depth/Isolation)
When instincts describe complex, multi-step processes that benefit from isolation:
- Debugging workflows
- Refactoring sequences
- Research tasks
Example:
debug-step1: "when debugging, first check logs"debug-step2: "when debugging, isolate the failing component"debug-step3: "when debugging, create minimal reproduction"debug-step4: "when debugging, verify fix with test"
→ Creates: debugger agent
What to Do
- Read all instincts from
~/.claude/homunculus/instincts/ - Group instincts by:
- Domain similarity
- Trigger pattern overlap
- Action sequence relationship
- For each cluster of 3+ related instincts:
- Determine evolution type (command/skill/agent)
- Generate the appropriate file
- Save to
~/.claude/homunculus/evolved/{commands,skills,agents}/
- Link evolved structure back to source instincts
Output Format
🧬 Evolve Analysis
==================
Found 3 clusters ready for evolution:
## Cluster 1: Database Migration Workflow
Instincts: new-table-migration, update-schema, regenerate-types
Type: Command
Confidence: 85% (based on 12 observations)
Would create: /new-table command
Files:
- ~/.claude/homunculus/evolved/commands/new-table.md
## Cluster 2: Functional Code Style
Instincts: prefer-functional, use-immutable, avoid-classes, pure-functions
Type: Skill
Confidence: 78% (based on 8 observations)
Would create: functional-patterns skill
Files:
- ~/.claude/homunculus/evolved/skills/functional-patterns.md
## Cluster 3: Debugging Process
Instincts: debug-check-logs, debug-isolate, debug-reproduce, debug-verify
Type: Agent
Confidence: 72% (based on 6 observations)
Would create: debugger agent
Files:
- ~/.claude/homunculus/evolved/agents/debugger.md
---
Run `/evolve --execute` to create these files.
Flags
--execute: Actually create the evolved structures (default is preview)--dry-run: Preview without creating--domain <name>: Only evolve instincts in specified domain--threshold <n>: Minimum instincts required to form cluster (default: 3)--type <command|skill|agent>: Only create specified type
Generated File Format
Command
---
name: new-table
description: Create a new database table with migration, schema update, and type generation
command: /new-table
evolved_from:
- new-table-migration
- update-schema
- regenerate-types
---
# New Table Command
[Generated content based on clustered instincts]
## Steps
1. ...
2. ...
Skill
---
name: functional-patterns
description: Enforce functional programming patterns
evolved_from:
- prefer-functional
- use-immutable
- avoid-classes
---
# Functional Patterns Skill
[Generated content based on clustered instincts]
Agent
---
name: debugger
description: Systematic debugging agent
model: sonnet
evolved_from:
- debug-check-logs
- debug-isolate
- debug-reproduce
---
# Debugger Agent
[Generated content based on clustered instincts]