drift-audit

Audits repository documentation and skills for drift against actual code and configuration.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/robritacca-dotcom/design-system --skill drift-audit-robritacca-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift-audit
Source: https://github.com/robritacca-dotcom/design-system/tree/main/.claude/skills/drift-audit
Command: npx skills add https://github.com/robritacca-dotcom/design-system --skill drift-audit-robritacca-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After structural or architectural changes, a repository's docs, skills, and README often silently fall out of sync with reality — referencing deleted scripts, moved files, or stale workflows that only fail when someone follows them. This Skill systematically verifies every self-description in the repo against how the code actually works. ## Core Features & Use Cases - Execution-based verification: Runs the commands and recipes docs prescribe (npm scripts, validator chains, multi-step workflows) rather than just reading them, catching instructions that would break on the next run. - Mechanical cross-checks: Greps for referenced commands, file paths, import specifiers, internal links, and hardcoded counts, then diffs them against package.json scripts, the exports map, and registries. - Skills self-audit: Reviews every SKILL.md for broken commands, stale paths, duplicated registry facts, and missing coverage of repeated workflows. - Use Case: After migrating a build step or renaming a route, run the audit to get a severity-grouped report (broken, stale, gaps, verified) with file paths, line numbers, and concrete fixes before the drift misleads contributors or consumers. ## Quick Start Ask the AI to run a drift audit on this repository to check whether the docs and skills are still up to date.

Frequently Asked Questions about drift-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my repository documentation is out of date?

Run a drift audit that cross-checks every command, file path, and import referenced in your docs against the real package.json scripts, exports map, and file system. It reports broken instructions, stale claims, and coverage gaps grouped by severity.

How to verify that documented npm scripts and commands still work?

The audit collects all npm run references across markdown files and skills, diffs them against the actual script list in every workspace, and executes multi-step recipes in a throwaway location to confirm they complete.

When should I run a documentation drift audit?

Run it after any structural or architectural change: a new build step, moved directory, changed dependency model, renamed route, or new published surface. It is also useful whenever you suspect docs and skills have fallen behind the code.

Does the drift audit fix the documentation problems it finds?

No, the report is the deliverable. It groups findings by severity with file paths and suggested fixes, then asks whether to apply them, since some findings are judgement calls rather than clear errors.

What are the limitations of automated documentation validation?

Build validators only catch mechanically checkable issues. Prose that asserts something false about the system, or instructions that fail only when followed, pass every validator — the drift audit exists to cover that layer by executing what docs prescribe.