drift-fix
Skill1 starsChanged 6 months agoMITView on GitHub
Apply fixes from the latest quarterly drift audit report. Use after drift-watcher-quarterly runs and produces a 01 - Daily Notes/<date> - Quarterly Drift Audit.md report.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- aribajahan/claude-skillstheir own version, first seen Sep 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- aribajahan/claude-skills★ 0same 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 repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditSkill
- brainstormSkill
- commit-message-writerSkill
- compile-topicSkill
- course-builderSkill
- daily-note-writerSkill
- deck-builderSkill
- diagnoseSkill
- forgeSkill
- git-bootstrapSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- lesson-content-writerSkill
- project-scaffolderSkill
- prototypeSkill
- retroSkill
- reviveSkill
- setup-pre-commitSkill
- specialist-creatorSkill
- sweep-inboxSkill
- tddSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- workflow-authorSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Read it top to bottom
- Distinctive: line 36
Don't bulk-fix without reading each finding - drift can be wrong
- Distinctive: line 37
Don't git rm files flagged as orphans without checking they're truly unused
- Distinctive: line 38
Don't skip the activity-log row - audit closures need history
≈ “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
Drift Fix
When to use
Triggers: fix the drift, apply the audit, close the drift report, drift-watcher said X is broken.
Load
- Find the latest drift report:
01 - Daily Notes/<YYYY-MM-DD> - Quarterly Drift Audit.md - Read it top to bottom
03 - Skills & Rules/Rules/playbook-refresh.md- for any 🔴 critical findings that are real bugs
Process
For each finding:
🔴 Critical
Apply playbook-refresh: read symptom, identify root cause, fix, verify, log. These usually mean a broken wikilink target file deleted, a CLAUDE.md over 200 lines, or a workflow referenced by trigger that doesn't exist.
🟡 Worth fixing
Direct fix per the suggestion in the report. Examples:
- Stale path reference → find/replace
- Ghost specialist → stub the missing file or remove the dangling delegates_to entry
⚪ Note
Acknowledge in the report but don't fix unless trivial.
After fixes
- Append an Activity Log row noting what got resolved and what was deferred
- Re-run drift-watcher manually (or wait for next quarter) to confirm fixes held
Don't
- Don't bulk-fix without reading each finding - drift can be wrong
- Don't
git rmfiles flagged as orphans without checking they're truly unused - Don't skip the activity-log row - audit closures need history
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.