vibe-drift

Project drift is detected by analyzing git history and current codebase files against original design intent documented in CLAUDE.md and SOUL.md. This process identifies divergent feature growth patterns and rising complexity to provide early warnings before architectural decay.

Codebase drift detection quantifies the percentage a repository has deviated from its original goals. You should run it during periodic health checks, release reviews, and governance audits to catch architectural divergence before it becomes costly.

Architecture drift is quantified by comparing current repository state against thresholds defined in governance.yaml files. The analysis computes a drift percentage and recommends whether to continue development, issue a warning, or trigger a full architecture audit.

Yes, CLAUDE.md and SOUL.md are required as baseline inputs. The code audit reads these files to establish the original project intent and identify forbidden directions before analyzing repository source files and git commit history.

Yes, git history analysis scans recent commit trajectories and code structure to detect feature growth patterns that violate forbidden directions. It extracts these constraints directly from your SOUL.md baseline documentation.

Drift detection is limited by the quality of baseline documentation and requires access to repository source files, git history, and governance thresholds. Without proper CLAUDE.md and SOUL.md files, the skill cannot establish the original intent needed to quantify deviations.