drift

Compare specification files against code to detect discrepancies.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/ronniepinnell/casper --skill drift-ronniepinnell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift
Source: https://github.com/ronniepinnell/casper/tree/main/skills/drift
Command: npx skills add https://github.com/ronniepinnell/casper --skill drift-ronniepinnell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies discrepancies between documented specifications and actual code and live system behavior, ensuring that developers are working with up-to-date and accurate information.

Core Features & Use Cases

  • Spec vs Code Comparison: Compares specifications against actual code and live system behavior.
  • Drift Detection: Reports on inconsistencies between specifications and code.
  • Use Case: Before building on a spec or as a periodic check, to ensure that the code matches the intended design.

Quick Start

Run the 'drift' command with the path to your spec file and the code path to compare.

Frequently Asked Questions about drift

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

FAQPage Schema
How do I check for code drift between my specifications and implementation?

To detect code drift, provide the path to your specification file and the corresponding code path for comparison. The tool identifies discrepancies between documented specs and actual code to ensure code integrity and alignment.

What is specification drift detection in software maintenance?

Specification drift detection identifies inconsistencies between documented specifications and actual code or live system behavior. It ensures developers work with accurate, up-to-date information during maintenance and integration tasks.

When should I run a spec vs code comparison?

Run a spec vs code comparison before building on a specification or as a periodic check to ensure code matches the intended design. This prevents accumulating discrepancies during ongoing maintenance and integration tasks.

Do I need both spec files and codebase access to detect alignment issues?

Yes, detecting alignment issues requires access to both specification files and the codebase. The tool compares these inputs directly to identify discrepancies and report on code integrity.

Can I use drift detection for live system behavior comparison?

Yes, drift detection compares specifications against actual code and live system behavior. This ensures your documentation accurately reflects both the static codebase and dynamic runtime operations.

How does code integrity checking apply to code review processes?

Code integrity checking applies to code reviews by identifying discrepancies between specifications and implementation before merging. It validates alignment with the intended design during maintenance and integration tasks.