instruction-drift
Skill94 starsChanged 6 months agoNo licenceArchived repositoryView on GitHub
Detect drift in instruction files and skills against upstream documentation sources. Checks when tracked GitHub issues close, reference pages change, or new platform features ship that aren't reflected locally. Use when asked to "check for drift", "are instructions up to date", "instruction drift", "check if gh-aw docs are current", "update instructions from upstream", "what changed upstream", or "have our instructions drifted". Also use proactively before major instruction file edits to ensure you're working with current information. Produces a drift report — never auto-edits files.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
In this repository11 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- android-wifi-deploySkill
- auth-token-safetySkill
- copilot-sdk-referenceSkill
- gh-aw-guideSkill
- health-monitoringSkill
- maui-ai-debuggingSkill
- multi-agent-orchestrationSkill
- performance-optimizationSkill
- processing-state-safetySkill
- release-notesSkill
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.