How do I install the Harness Drift From History skill?

Run npx skillmds@latest add ruvnet/harness-drift-from-history in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Harness Drift From History safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Harness Drift From History?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Harness Drift From History free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Harness Drift From History?

ruvnet (@ruvnet) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Harness Drift From History by ruvnet

Name: Harness Drift From History
Rating: 4.5 (4 reviews)
Author: ruvnet

Harness Drift From History

One-command drift detection. Composes audit-list + oia-audit + audit-trend into a single primitive — finds the most recent audit in `metaharness-audit` namespace, runs a fresh audit against the current repo, diffs them via ADR-152 §3.1 similarity, and alerts when structural distance crosses `--threshold`. Iter 53 of ADR-150 deep integration.

ruvnet Updated Sep 8, 2026

File contents

The natural ops question after running oia-audit weekly is "did anything drift?" Before this skill, the answer required a three-step sequence:

npx ruflo metaharness audit-list --format json   # → pick a key by hand
npx ruflo metaharness oia-audit --format json > /tmp/curr.json
npx ruflo metaharness audit-trend \
  --baseline-key <picked-key> --current /tmp/curr.json \
  --alert-on-distance-below 0.95

This skill collapses it into one command:

npx ruflo metaharness drift-from-history --threshold 0.95

What it does

Lists records from metaharness-audit namespace via audit-list.mjs
Picks the most recent record by startedAt (or --baseline-since 7d skips anything newer than 7 days)
Runs a fresh oia-audit against the current path
Diffs the two via audit-trend, applying --alert-on-distance-below ${threshold}
Returns the structured drift report

Architectural constraint inheritance (ADR-150)

Constraint	How drift-from-history satisfies it
Removable	Pure subprocess composition over existing scripts — no new `@metaharness/*` import
Optional	If oia-audit reports `degraded:true`, this skill exits 3 with a degraded payload
Graceful	Empty audit history → exit 2 with hint to seed it; never crashes
CI-gate	Smoke step 17z16 anchors the dispatcher entry + subcommand listing

Exit codes

0 — similarity ≥ threshold (or threshold not crossed)
1 — drift detected: similarity < threshold (alert fired)
2 — config error (no history, audit-list failed)
3 — upstream metaharness absent (degraded payload returned)

Example

$ npx ruflo metaharness drift-from-history --threshold 0.95
# drift-from-history

Baseline:        audit-2026-06-16T22-58-47-840Z
Current:         2026-06-16T23:05:02.231Z

Structural similarity: 1 (near-identical)
Distance:              0

✓ similarity ≥ 0.95 — OK

Implementation

scripts/drift-from-history.mjs

Source: ruvnet/ruflo → plugins/ruflo-metaharness/skills/harness-drift-from-history/SKILL.md

---name: harness-drift-from-historydescription: One-command drift detection. Composes audit-list + oia-audit + audit-trend into a single primitive — finds the most recent audit in `metaharness-audit` namespace, runs a fresh audit against the current repo, diffs them via ADR-152 §3.1 similarity, and alerts when structural distance crosses `--threshold`. Iter 53 of ADR-150 deep integration.---The natural ops question after running `oia-audit` weekly is "did anything drift?" Before this skill, the answer required a three-step sequence:```bashnpx ruflo metaharness audit-list --format json # → pick a key by handnpx ruflo metaharness oia-audit --format json > /tmp/curr.jsonnpx ruflo metaharness audit-trend \ --baseline-key <picked-key> --current /tmp/curr.json \ --alert-on-distance-below 0.95```This skill collapses it into one command:```bashnpx ruflo metaharness drift-from-history --threshold 0.95```## What it does1. Lists records from `metaharness-audit` namespace via audit-list.mjs2. Picks the most recent record by `startedAt` (or `--baseline-since 7d` skips anything newer than 7 days)3. Runs a fresh `oia-audit` against the current path4. Diffs the two via audit-trend, applying `--alert-on-distance-below ${threshold}`5. Returns the structured drift report## Architectural constraint inheritance (ADR-150)| Constraint | How drift-from-history satisfies it ||---|---|| Removable | Pure subprocess composition over existing scripts — no new `@metaharness/*` import || Optional | If oia-audit reports `degraded:true`, this skill exits 3 with a degraded payload || Graceful | Empty audit history → exit 2 with hint to seed it; never crashes || CI-gate | Smoke step 17z16 anchors the dispatcher entry + subcommand listing |## Exit codes- 0 — similarity ≥ threshold (or threshold not crossed)- 1 — drift detected: similarity < threshold (alert fired)- 2 — config error (no history, audit-list failed)- 3 — upstream metaharness absent (degraded payload returned)## Example```bash$ npx ruflo metaharness drift-from-history --threshold 0.95# drift-from-historyBaseline: audit-2026-06-16T22-58-47-840ZCurrent: 2026-06-16T23:05:02.231ZStructural similarity: 1 (near-identical)Distance: 0✓ similarity ≥ 0.95 — OK```## Implementation[`scripts/drift-from-history.mjs`](../../scripts/drift-from-history.mjs)---**Source:** [`ruvnet/ruflo`](https://github.com/ruvnet/ruflo) → `plugins/ruflo-metaharness/skills/harness-drift-from-history/SKILL.md`

Frequently asked questions