detecting-drift

Compare artifact state against validation baselines to produce drift reports.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/0xHoneyJar/construct-observer --skill detecting-drift
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: detecting-drift
Source: https://github.com/0xHoneyJar/construct-observer/tree/main/skills/detecting-drift
Command: npx skills add https://github.com/0xHoneyJar/construct-observer --skill detecting-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Show what changed since the last validation of a specific artifact. Queries git history and feedback events to produce a drift report with a computed confidence score. Read-only — does NOT modify any files.

Core Features & Use Cases

  • Reads validation metadata and git history to generate a drift report.
  • Compares artifact state across paths and computes a confidence score.
  • Read-only workflow that does not write to frontmatter.

Quick Start

Run /drift {artifact-path} to generate a drift report for the artifact.

Frequently Asked Questions about detecting-drift

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

FAQPage Schema
How do I detect drift in artifact quality using git history?▼

Detect drift by comparing current artifact state to the last validation baseline. The skill queries git history and feedback events to generate a drift report with a computed confidence score.

What is artifact drift and how does a confidence score help monitor it?▼

Artifact drift is a change in artifact quality since the last validation. A computed confidence score quantifies this drift by analyzing validation metadata, git history, and user feedback events.

How do I generate a drift report for a specific directory path?▼

Generate a drift report by running the read-only drift workflow on a specified artifact path. It compares the current state against validation metadata to produce a confidence score without modifying frontmatter.

Does detecting drift modify frontmatter or write to artifact files?▼

Detecting drift does not modify frontmatter or write to files. It implements a strictly read-only workflow that queries git history and feedback events to compute a confidence score.

Can I use user feedback events to validate artifact changes over time?▼

Use user feedback events to validate artifact changes by applying them alongside git history. The workflow compares current states to baselines and produces a drift report with a confidence score.

When should I avoid using an automated drift report for artifact validation?▼

Avoid automated drift reports when you lack access to git history or feedback events. The workflow requires both to compute a confidence score and compare against the last validation baseline.