drift-audit

Categorize inconsistent code implementations into drift variants for unification.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/chris-arsenault/svap --skill drift-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift-audit
Source: https://github.com/chris-arsenault/svap/tree/main/.claude/skills/drift-audit
Command: npx skills add https://github.com/chris-arsenault/svap --skill drift-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and categorizes technical drift within a codebase, where the same concept is implemented in multiple inconsistent ways, helping to streamline development and reduce technical debt.

Core Features & Use Cases

  • Automated Discovery: Scans code to find all instances of potential drift.
  • Variant Categorization: Groups similar implementations into distinct variants.
  • Impact Assessment: Rates the severity and scope of each drift area.
  • Actionable Recommendations: Provides specific guidance for unification.
  • Use Case: When a project has grown organically, different developers might implement similar features (like modals or data fetching) in slightly different ways. This skill helps find all these variations, assess their impact, and suggest a unified approach.

Quick Start

Run a technical drift audit on the current project's codebase.

Frequently Asked Questions about drift-audit

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

FAQPage Schema
How do I find inconsistent code implementations of the same concept across multiple files?

Code drift refers to the phenomenon where the same concept is implemented in multiple inconsistent ways across a codebase. Detecting this drift helps streamline development and reduce accumulated technical debt by identifying areas for unification.

How do I audit my codebase for technical drift and reduce technical debt?

To audit for technical drift, scan your code to discover all instances of inconsistent implementations. The audit categorizes these variants, rates their severity and scope, and provides actionable recommendations for unifying the codebase.

Do I need to install any specific tools to perform a semantic code drift analysis?

Yes, performing a semantic code drift analysis requires the drift tool to be installed and configured. This dependency is necessary for the Skill to analyze code structure, dependencies, and naming conventions accurately.

What is the best way to assess the impact of inconsistent naming conventions and code structures?

The best way to assess the impact of inconsistent code structures is to use an automated drift discovery tool. It categorizes similar implementations into variants and rates the severity and scope of each drift area to prioritize refactoring efforts.

Can a drift detection audit suggest specific code refactoring steps for unification?

Yes, a drift detection audit provides actionable recommendations for unification. After grouping similar implementations into distinct variants, it delivers specific guidance to streamline development and resolve technical debt.