ad-drift

Detect discrepancies between repository documentation and actual codebase implementation.

1|Updated May 8, 2026

Search Tags:#architecture #documentation #adr #audit #compliance #drift

Ready to run

npx skills add https://github.com/alexandremendoncaalvaro/agentic-development --skill ad-drift

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ad-drift
Source: https://github.com/alexandremendoncaalvaro/agentic-development/tree/main/.agents/skills/ad-drift
Command: npx skills add https://github.com/alexandremendoncaalvaro/agentic-development --skill ad-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of documentation rot by identifying inconsistencies between a repository's operational documentation (AGENTS.md, ARCHITECTURE.md, ADRs) and the actual state of the codebase.

Core Features & Use Cases

Automated Drift Detection: Compares stack definitions, build commands, and architectural boundaries against actual project files.
Compliance Auditing: Ensures ADRs and specs follow established numbering, status, and cross-reference rules.
Use Case: Run this audit before a major release to ensure that your ARCHITECTURE.md accurately reflects the current directory structure and that all ADRs are correctly linked and status-updated.

Quick Start

Ask the agent to run the ad-drift skill to audit the repository and report any inconsistencies between the documentation and the code.

Frequently Asked Questions about ad-drift

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

FAQPage Schema

How do I audit documentation drift in my codebase?▼

Documentation drift occurs when operational docs like ARCHITECTURE.md and ADRs become inconsistent with the actual codebase structure. Automated drift detection analyzes these files against the repository to report misaligned build commands, stack definitions, and architectural boundaries.

How do I check ADR compliance with project workflow rules?▼

Checking ADR compliance involves validating Architecture Decision Records against established numbering, status, and cross-reference rules. An audit verifies that all ADRs are correctly linked and status-updated according to your project-specific documentation standards.

Can I use an audit tool to verify ARCHITECTURE.md reflects my current directory structure?▼

Yes, you can verify that ARCHITECTURE.md reflects your current directory structure by running an audit. It compares your architectural boundaries and stack definitions against actual project files to ensure structural alignment before major releases.

What is the best way to prevent documentation rot in a software repository?▼

Preventing documentation rot requires regularly auditing operational documentation against the codebase. Identifying discrepancies early ensures that specs, architectural boundaries, and procedural guidelines remain aligned with the actual implementation.

Does the drift audit modify my repository files during compliance checking?▼

No, the drift audit does not modify your repository files. It performs a read-only analysis of your documentation and codebase to report discrepancies and validate compliance without altering any project files.