drift

Analyze definition files for convergence and divergence patterns using Git history.

14|6|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/tyevans/tackline --skill drift-tyevans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift
Source: https://github.com/tyevans/tackline/tree/main/skills/workflows/drift
Command: npx skills add https://github.com/tyevans/tackline --skill drift-tyevans

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill identifies inconsistencies and opportunities for standardization across multiple definition files, ensuring better maintainability and knowledge sharing.

Core Features & Use Cases

  • Detects shared patterns: Finds common sections and frontmatter fields across files.
  • Identifies divergence: Highlights sections present in some files but missing in others.
  • Flags cross-pollination needs: Alerts when changes in one file should propagate to similar files.
  • Use Case: After updating several agent definitions, use drift to ensure that new safety guidelines or preamble structures are consistently applied across all of them.

Quick Start

Use the drift skill to analyze workflow skills for definition convergence.

Frequently Asked Questions about drift

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

FAQPage Schema
How do I detect definition convergence and divergence across multiple agent files?

To detect definition convergence and divergence, analyze definition files by parsing their content, section headers, and Git history to report on structural similarities and cross-pollination opportunities.

What is definition cross-pollination in code quality management?

Definition cross-pollination occurs when changes in one definition file should propagate to similar files to maintain consistency. Identifying this helps manage standardization and ensures better maintainability and knowledge sharing across a codebase.

How do I check for missing sections and inconsistencies across agent definitions?

To check for missing sections and inconsistencies, analyze the files to identify divergence patterns, highlighting sections present in some files but missing in others. This ensures new safety guidelines or preamble structures are consistently applied.

Does this definition analysis require Git history to identify shared patterns?

Yes, this definition analysis requires Git history to effectively identify shared patterns and structural similarities. Parsing Git history alongside file content and section headers reports on structural similarities and potential updates.

What is the best way to ensure consistency after refactoring multiple skill definitions?

The best way to ensure consistency after refactoring multiple skill definitions is to analyze the files for divergence patterns. This flags cross-pollination needs and alerts you when changes in one file should propagate to similar files.