implementation-drift-check

Detect deviations between code implementation and specifications using Python analysis.

6|Updated Feb 13, 2026

Search Tags:#devops #code review #drift detection #implementation verification #specification compliance

Ready to run

npx skills add https://github.com/damianpapadopoulos/auto-claude-skills --skill implementation-drift-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-drift-check
Source: https://github.com/damianpapadopoulos/auto-claude-skills/tree/main/skills/implementation-drift-check
Command: npx skills add https://github.com/damianpapadopoulos/auto-claude-skills --skill implementation-drift-check

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The implementation-drift-check Skill helps identify and manage drift between code implementation and its corresponding specifications or plans, ensuring alignment and integrity.

Core Features & Use Cases

Drift Detection: Compares current implementation against specs or plans to find deviations.
Automated Checks: Runs during code review and shipping phases to catch drift proactively.
Custom Invocation: Explicitly invoke to check drift during implementation stages.
Multi-Source Analysis: Considers various sources like OpenSpec changes, live intent documents, and legacy specifications.

Quick Start

Run the implementation-drift-check skill to verify that the implementation 'feature-x' aligns with its specification.

Frequently Asked Questions about implementation-drift-check

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

FAQPage Schema

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

Implementation drift detection compares current code against specs or plans to find deviations. This skill uses git and filesystem access to retrieve artifacts, analyzing them with Python to report alignment issues during code review or shipping phases.

When do I need specification compliance checks during development?▼

Specification compliance checks are needed during code review and shipping phases to catch drift proactively. You can also explicitly invoke drift detection during implementation stages to verify that your code aligns with OpenSpec changes or live intent documents.

How do I verify my code aligns with its specification using git?▼

You can verify code alignment by running a drift detection skill that retrieves artifacts via git and filesystem access. It analyzes your implementation against specifications or plans using Python, identifying and reporting deviations for code review.

Do I need Python and git to run implementation drift detection?▼

Yes, you need Python and git to run implementation drift detection. The skill requires git and filesystem access for artifact retrieval and diffing, while Python is utilized for the actual analysis and reporting of specification deviations.

Can I use this drift detection skill with legacy specifications?▼

Yes, you can use this drift detection skill with legacy specifications. It performs multi-source analysis, considering various inputs like OpenSpec changes, live intent documents, and legacy specifications to identify deviations in your implementation.

What's the best way to automate drift checks during the shipping phase?▼

The best way to automate drift checks during shipping is to run a specification compliance skill that compares implementation against plans. This proactively catches drift using Python analysis and git artifact retrieval during code review and shipping phases.