extract-patterns
Skill9 starsChanged 9 months agoMITView on GitHub
Extract learned patterns from session - invoked automatically by finishing-a-development-branch or manually anytime
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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 22
Use /sp-ecc:learn command to extract patterns:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Extract Patterns
Overview
Wraps ECC's continuous-learning-v2 system to extract and save useful patterns from development sessions.
Auto-invoked by: finishing-a-development-branch skill Can be invoked: Manually anytime to save learning Purpose: Build institutional knowledge over time
Announce at start: "I'm using the extract-patterns skill to learn from this session."
The Process
Step 1: Invoke Pattern Extraction
Use /sp-ecc:learn command to extract patterns:
/sp-ecc:learnThis analyzes the current session for:
- Successful problem-solving approaches
- Useful code patterns
- Effective debugging strategies
- Language/framework insights
- Common mistake avoidance
Step 2: Review Extracted Patterns
The learning system will show patterns with confidence scores.
Review criteria:
- Is the pattern actually useful?
- Is the confidence score appropriate?
- Would this help in future sessions?
Step 3: Save to Instinct System
Patterns are automatically saved to the instinct system.
View saved patterns:
/sp-ecc:instinct-statusStep 4: Optional - Evolve into Skills
For mature patterns (high confidence, multiple uses):
/sp-ecc:evolveThis clusters related patterns into reusable skills.
Integration with Workflow
Auto-Invoked:
finishing-a-development-branch:
1. Verify tests pass
2. Sync documentation
3. Extract patterns (THIS SKILL) ← Auto-invoked
4. Generate changelist
5. Present optionsManual Invocation:
Any time during development:
- "Can you extract patterns from what we just did?"
- Skill invoked
- Patterns saved for futureOpt-Out
To disable auto-invocation in finishing workflow:
See: docs/integration/OPT-OUT.md
Exporting/Importing Patterns
Export patterns to file:
/sp-ecc:instinct-exportImport patterns from file:
/sp-ecc:instinct-importUseful for:
- Sharing patterns across teams
- Backing up learned knowledge
- Transferring patterns between projects
Quick Reference
| Command | Purpose |
/sp-ecc:learn | Extract patterns from session |
/sp-ecc:instinct-status | View saved patterns |
/sp-ecc:instinct-export | Export to file |
/sp-ecc:instinct-import | Import from file |
/sp-ecc:evolve | Cluster patterns into skills |
Remember
- Patterns accumulate over time
- Higher confidence = more proven
- Export periodically for backup
- Share successful patterns with team
Remember: This builds institutional knowledge. The more you use it, the smarter the system becomes.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- andrewclark88/skills★ 1same name
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 repository55 other files it gives its agents.
- backend-patternsSkill
- brainstormingSkill
- clarify-firstSkill
- clickhouse-ioSkill
- coding-standardsSkill
- continuous-learning-v2Skill
- dart-patternsSkill
- dart-testingSkill
- dispatching-parallel-agentsSkill
- django-patternsSkill
- django-securitySkill
- django-tddSkill
- django-verificationSkill
- eval-harnessSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- flutter-patternsSkill
- flutter-verificationSkill
- frontend-designSkill
- frontend-patternsSkill
- golang-patternsSkill
- golang-testingSkill
- iterative-retrievalSkill
- java-coding-standardsSkill
- jpa-patternsSkill
- logging-best-practicesSkill
- model-routingSkill
- postgres-patternsSkill
- python-patternsSkill
- python-testingSkill
- rails-patternsSkill
- rails-securitySkill
- rails-tddSkill
- rails-verificationSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- ruby-patternsSkill
- ruby-testingSkill
- security-reviewSkill
- security-scanSkill
- skill-stocktakeSkill
- springboot-patternsSkill
- springboot-securitySkill
- springboot-tddSkill
- springboot-verificationSkill
- strategic-compactSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- using-sp-eccSkill
- verification-before-completionSkill
- verification-loopSkill
- writing-plansSkill
- writing-skillsSkill
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.

