agentleFS
kunalsurikunalsuri/ai-fication-kit/.claude/skills/check-drift/SKILL.md

check-drift

Skill3 starsChanged 4 months agoApache-2.0View on GitHub

Run verification and drift checks on the AI knowledge-base to identify missing documentation or stale references.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the mechanical verification and drift analysis to inspect the state of the ai/ knowledge-base:

    line 8
  2. Very specific:

    Run the path verifier: node install.mjs verify .

    line 10
  3. Very specific:

    Run the drift detector with git history comparison: node install.mjs drift .

    line 12
  4. Distinctive:

    Run git status to inspect modified and untracked files.

    line 14
  5. Distinctive:

    If any issues are reported, or if git status reveals newly added or modified source files/templates that are not yet covered in the maps:

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Copyright (c) 2026 Kunal Suri (CEA LIST). All rights reserved. -->

Run the mechanical verification and drift analysis to inspect the state of the ai/ knowledge-base:

  1. Run the path verifier: node install.mjs verify . --strict
  2. Run the drift detector with git history comparison: node install.mjs drift . --git --strict
  3. Run git status to inspect modified and untracked files.

If any issues are reported, or if git status reveals newly added or modified source files/templates that are not yet covered in the maps:

  • Draft updates to ai/guide/MODULE_MAP.md or ai/guide/FEATURE_MAP.md to map new folders, files, or features, or to update stale verified dates.
  • Mark any changes you draft as [inferred].
  • Report findings to the user and outline what needs their manual review.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.