drift

Detect architectural drift in code modules using git history and metrics.

71|7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/mbwsims/claude-universe --skill drift-mbwsims
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift
Source: https://github.com/mbwsims/claude-universe/tree/main/skills/drift
Command: npx skills add https://github.com/mbwsims/claude-universe --skill drift-mbwsims

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often cannot see how modules evolve over time, leading to hidden scope creep, layer violations, and purpose shifts that degrade maintainability.

Core Features & Use Cases

  • Analyze a specified module or automatically select candidates with the most change.
  • Compare original and current versions using git history, export/import counts, and line metrics.
  • Classify drift types such as scope creep, god module, layer violation, or purpose shift.
  • Generate a detailed drift report with key commits and actionable recommendations.

Quick Start

Ask the drift skill to analyze the module src/utils/logger.ts for architectural drift.

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 and scope creep in my codebase?

To detect architectural drift, you can analyze a module's original and current state using git history, export/import counts, and line metrics to quantify changes and classify drift types like scope creep or layer violations.

What is architectural drift in software engineering?

Architectural drift occurs when modules evolve over time with hidden scope creep, layer violations, or purpose shifts, which degrades maintainability. It is detected by comparing a module's original and current versions to classify the drift type.

Can I analyze git history to find god modules and layer violations?

Yes, you can analyze git history to compare original and current module versions, using export/import analysis and line count metrics to classify drift types such as god modules, layer violations, and purpose shifts.

How do I generate a drift assessment report for a specific file?

You generate a drift assessment report by analyzing a specified module, like src/utils/logger.ts, to compare its original and current state, identifying key commits and providing actionable recommendations for architectural drift.

Does this drift analysis work with any codebase directory?

Yes, drift analysis applies to any codebase file or directory where scope creep, layer violations, or purpose shifts may have occurred, using git history and line count metrics to quantify the changes.