What problem does it solve?
Answering "did anything drift?" in a repository previously required manually chaining three separate commands: listing past audits, running a fresh audit, and diffing them with a similarity threshold. This Skill collapses that sequence into a single command that automatically picks the baseline, runs the comparison, and alerts when structural distance crosses a threshold.
Core Features & Use Cases
- One-command drift detection: Composes audit-list, oia-audit, and audit-trend into a single primitive that finds the most recent audit in the metaharness-audit namespace and diffs it against a fresh audit.
- Configurable baseline and threshold: Use --baseline-since to skip records newer than a given window (e.g. 7d) and --threshold to set the similarity alert level (e.g. 0.95).
- Structured exit codes for CI: Returns 0 when similarity meets the threshold, 1 on detected drift, 2 on missing history, and 3 when the upstream metaharness is degraded, making it suitable for pipeline gates.
- Use Case: Run weekly in CI to compare the current repository structure against last week's audit and fail the build when structural similarity drops below 0.95.
Quick Start
Ask the AI to run a drift check against the most recent stored audit with a similarity threshold of 0.95 and report whether the repository structure has drifted.
