plugins/continuous-learning/skills/evolve/SKILL.md
Cluster related instincts into higher-order skills, commands, or agents
npx skillsauth add jason-hchsieh/marketplace evolveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are evolving clusters of related instincts into higher-order knowledge structures.
Instincts can evolve into:
Read all instincts from .claude/learning/instincts/ and identify clusters:
For each viable cluster (3+ related instincts), propose:
## Evolution Candidate: [Name]
### Source Instincts
- instinct-1 (confidence: X.X)
- instinct-2 (confidence: X.X)
- instinct-3 (confidence: X.X)
### Recommended Evolution
**Type**: [Skill/Command/Agent/Convention]
**Rationale**: [Why this type fits]
### Preview
[Show what the evolved artifact would look like]
After user approval, create the appropriate artifact:
For Skills: Create .claude/learning/evolved/skills/[name]/SKILL.md
For Commands: Create .claude/learning/evolved/commands/[name].md
For Agents: Create .claude/learning/evolved/agents/[name].md
For Conventions: Append to .claude/learning/evolved/conventions.md
Move evolved instincts to .claude/learning/instincts/archived/ with reference to what they became.
| Cluster Size | Avg Confidence | Recommendation | |--------------|----------------|----------------| | 3-4 | 0.5+ | Consider evolving | | 5-7 | 0.6+ | Strong candidate | | 8+ | Any | Definitely evolve |
## Evolution Report
### Clusters Identified
1. [Cluster Name] - X instincts, avg confidence Y.Y
2. [Cluster Name] - X instincts, avg confidence Y.Y
### Proposed Evolutions
#### 1. [Name] → Skill
**Source instincts**: [list]
**Preview**:
---
name: [skill-name]
description: [description]
---
[Skill content preview]
---
### Actions Required
- [ ] Approve evolution of [cluster] → [type]
- [ ] Review and customize generated artifact
- [ ] Archive source instincts
Proceed with evolution? (specify which clusters)
tools
Bootstrap versioning for a project - detect project type, initialize git-cliff config, and generate initial CHANGELOG.md using semantic versioning
development
Validate version consistency across all project files, check semver format, git tag alignment, and changelog synchronization per https://semver.org/
tools
Generate or update CHANGELOG.md using git-cliff from conventional commit history - see https://git-cliff.org/docs/category/usage
tools
Bump the project version following semver, update all version files per https://semver.org/