drift

Detect architectural drift across code, documentation, ADRs, and dependencies.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/0xHarbs/agent-setup --skill drift-0xharbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift
Source: https://github.com/0xHarbs/agent-setup/tree/main/claude/skills/lifecycle/drift
Command: npx skills add https://github.com/0xHarbs/agent-setup --skill drift-0xharbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural drift detection between the codebase and its own documentation, ADRs, CLAUDE.md conventions, and dependency health. It reports violations, stale docs, and schema-code mismatches without performing any fixes.

Core Features & Use Cases

  • Surface drift across ADRs, CLAUDE.md conventions, dependencies, and documentation to keep systems aligned.
  • Generate actionable findings and a dated drift report for trend analysis and housekeeping.
  • Use Case: Run a full drift scan before releases to identify divergences between code and its docs.

Quick Start

Run the drift workflow to generate a full report and review findings.

Frequently Asked Questions about drift

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

FAQPage Schema
How do I detect architectural drift between my codebase and documentation?

Architectural drift detection scans your codebase against ADRs, CLAUDE.md conventions, and documentation to surface violations and schema-code mismatches. It generates actionable findings and a dated drift report for trend analysis without applying any code changes.

What is the best way to check ADR compliance before a release?

Checking ADR compliance before a release involves running a full drift scan across your architecture decision records and CLAUDE.md rules. The scan identifies divergences between your code and its governing conventions, recording findings to .context/drift-reports for review.

Can I track schema-code alignment and dependency health over time?

You can track schema-code alignment and dependency health over time using historical drift tracking. The workflow records dated drift reports to .context/drift-reports, enabling trend analysis and housekeeping across parallel checks.

Does architectural drift analysis automatically fix stale documentation?

Architectural drift analysis does not automatically fix stale documentation or codebase violations. It operates in a read-only capacity to report drift across dependencies, docs, and schema-code alignment, leaving the actual remediation to the developer.

When do I need to run an architectural drift scan on my project?

You need to run an architectural drift scan when you want to verify that your codebase remains aligned with its ADRs, CLAUDE.md conventions, and documentation before major releases. It surfaces stale docs and dependency health issues for housekeeping.

Why does my codebase diverge from its CLAUDE.md conventions and ADRs?

Your codebase diverges from CLAUDE.md conventions and ADRs due to untracked changes during development. Running a drift analysis identifies these specific architectural violations and schema-code mismatches, providing an optional summary for code reviews.