check-drift

Detect specification drift between pull requests and project SDD documents.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/g-bastianelli/nuthouse --skill check-drift-g-bastianelli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-drift
Source: https://github.com/g-bastianelli/nuthouse/tree/main/acid-prophet/skills/check-drift
Command: npx skills add https://github.com/g-bastianelli/nuthouse --skill check-drift-g-bastianelli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Skill Unit "check-drift" solves the problem of specification drift by providing an automated, rigorous review process to detect and prevent differences between a Pull Request (PR) and its associated Specification and Constraints Documentation.

Core Features & Use Cases

  • Detection of Specification Drift: Automatically checks the code changes against the SDD (Specification and Design Document) of the project.
  • Prevention of Unwanted Changes: Flags changes that may violate project specifications before they reach the production stage.
  • Efficient PR Comment Posting: Can post the structured drift report directly as a PR comment, facilitating quicker issue resolution.
  • Use Case: Before creating a PR, you can use "check-drift" to ensure that the changes adhere to the specifications laid out in the documentation, helping to maintain high-quality code.

Quick Start

Before opening a Pull Request, run acid-prophet:check-drift to verify code compliance with project specifications and ensure there's no drift.

Frequently Asked Questions about check-drift

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

FAQPage Schema
How do I detect specification drift in a pull request?

Specification drift detection works by performing file diff analysis and data comparison against the project's SDD. It automatically identifies discrepancies between the code changes and the documented acceptance criteria and constraints.

What is the best way to ensure code compliance with project specifications before merging?

The best way to ensure code compliance is to run an automated drift detection check before creating a PR. This verifies that your changes adhere to the specifications laid out in the documentation, preventing unwanted modifications from advancing.

Does specification drift detection require access to specific project management platforms?

Yes, automated specification drift detection requires access to git repositories and Linear project context. These dependencies provide the necessary PR file diffs and project management data to compare against the SDD.

Can I post the specification drift report directly as a PR comment?

Yes, you can post the structured specification drift report directly as a PR comment. This functionality facilitates quicker issue resolution by making the code review checks immediately visible within the pull request.

When should I run an automated specification compliance check?

You should run an automated specification compliance check before opening a Pull Request. Running it pre-PR ensures that your code changes are validated against the SDD acceptance criteria and constraints, preventing specification drift early in the development cycle.