drift-audit

Audit git diffs against a contract file to detect unauthorized code changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify unauthorized changes in code implementations, ensuring that the code sticks to the approved plan and contract.

Core Features & Use Cases

  • Scope Drift Detection: Identifies any changes that are outside the approved implementation plan.
  • Authorization Verification: Confirms that only authorized changes are implemented.
  • Pre-Code Review Audit: Provides a safety check before the final code review.

Quick Start

Run the drift-audit skill on the diff for this branch to check for unauthorized changes.

Frequently Asked Questions about drift-audit

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

FAQPage Schema
How do I detect scope drift in a git diff before a code review?

Scope drift detection identifies unauthorized changes in a git diff by comparing code changes against a frozen contract file. This verifies that only authorized modifications are implemented before the final code review.

What is implementation scope auditing in software engineering?

Implementation scope auditing verifies code changes against a frozen contract to confirm only authorized modifications are implemented. It flags any scope drift outside the approved plan before the final code review.

How do I verify code changes against a frozen contract file?

You verify code changes against a frozen contract by analyzing the git diff and comparing it to the contract file. This confirms that only authorized changes are implemented and highlights any scope drift.

Do I need git to run a code review audit for unauthorized changes?

Yes, you need git to run this code review audit because the process requires git diff analysis to compare branch changes against the frozen contract file. Without git, the diff analysis cannot be performed.

When should I run an implementation audit during the development workflow?

You should run an implementation audit as a pre-code review safety check. Running it at this stage identifies unauthorized changes and scope drift early, ensuring the code sticks to the approved plan before final review.