drift-guard

Generate ESLint, ast-grep, and TypeScript rules to prevent technical drift.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically generates machine-enforceable guardrails (like ESLint rules and ast-grep patterns) to prevent technical drift in codebases after unification, ensuring consistency and adherence to canonical patterns.

Core Features & Use Cases

  • Automated Rule Generation: Creates ESLint, ast-grep, and TypeScript configuration rules based on existing codebase patterns.
  • Prioritized Enforcement: Focuses on hard, machine-enforceable protections before documentation.
  • Drift Prevention: Ensures that code does not revert to old, undesirable patterns after a unification process.
  • Use Case: After unifying a codebase to use a new state management library, this Skill generates ESLint rules to ban imports of the old library and enforce the correct usage patterns of the new one.

Quick Start

Use the drift-guard skill to generate ESLint rules to prevent the use of deprecated components in the codebase.

Frequently Asked Questions about drift-guard

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

FAQPage Schema
How do I prevent code drift after refactoring a TypeScript codebase?

You can prevent code drift by generating automated guardrails such as ESLint rules, ast-grep patterns, and TypeScript configuration constraints that enforce canonical patterns and block deprecated code.

How do I generate ESLint rules to ban imports of deprecated components?

Generating ESLint rules to ban deprecated component imports requires analyzing existing code, unification logs, and project configuration to define precise, machine-enforceable constraints that prevent technical drift.

What is the best way to enforce canonical code patterns automatically?

The best way to enforce canonical code patterns automatically is prioritizing hard, machine-enforceable protections like ast-grep rules and TypeScript configuration before relying on documentation.

Can I use ast-grep rules to enforce new state management library usage?

Yes, you can use ast-grep rules alongside ESLint and TypeScript configuration to enforce new state management library usage and ban old library imports after a codebase unification process.

Does drift prevention require analyzing existing code and unification logs?

Yes, drift prevention requires analysis of existing code, unification logs, and project configuration to define the precise constraints needed for machine-enforceable guardrails.