sheal-drift
Skill0 starsChanged 7 months agoMITView on GitHub
Detect learning drift — learnings that aren't being applied. Suggests promotions to CLAUDE.md invariants or .claude/rules/.
- Installs packages
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- aif-analyzeSkill
- aif-enhanceSkill
- aif-evolveSkill
- aif-feedbackSkill
- aif-ingestSkill
- aif-learnSkill
- aif-pulseSkill
- aiframework-learnSkill
- aiframework-reviewSkill
- aiframework-shipSkill
- aif-readySkill
- aif-researchSkill
- aif-reviewSkill
- aif-shipSkill
- aif-statusSkill
- retroSkill
- sheal-askSkill
- sheal-checkSkill
- sheal-retroSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 38
Check if it appears in CLAUDE.md invariants already
- Very specific: line 39
Check if a .claude/rules/ file covers it
- Distinctive: line 40
Check frequency of drift (how often the same learning is violated)
- Distinctive: line 51
Ask: "Found N learnings with persistent drift.
- Distinctive: line 54
Add to CLAUDE.md Invariants section via Edit tool
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
/sheal-drift — Drift Detection
Prerequisites
command -v sheal >/dev/null 2>&1 && sheal --version 2>/dev/null || echo "sheal not installed — run: npm install -g @liwala/sheal"Step 0: Telemetry (silent, non-blocking)
aiframework-telemetry skill_invoked skill=sheal-drift 2>/dev/null || trueStep 1: Check Drift
sheal drift --last 10 --format json --project . 2>/dev/null || echo '{"error": "sheal drift failed"}'Step 2: Analyze Patterns
For each drifted learning:
- Check if it appears in CLAUDE.md invariants already
- Check if a
.claude/rules/file covers it - Check frequency of drift (how often the same learning is violated)
Step 3: Promotion Recommendations
Apply these rules:
- Drift on same learning 3+ times → promote to CLAUDE.md invariant
- Drift in specific file area → create
.claude/rules/<domain>.md - No drift, healthy learning → keep as-is in sheal
Step 4: Apply Promotions (with approval)
Ask: "Found N learnings with persistent drift. Promote to permanent rules?"
For each approved promotion:
- Add to CLAUDE.md Invariants section via Edit tool
- Or create new
.claude/rules/file - Mark the sheal learning as
promoted
Step 5: Report
| Learning | Drift Count | Action |
| ... | N | Promoted/Keep/Dismissed |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

