Skill119 repo starsupdated today

upgrade-harness

The upgrade-harness skill detects and applies changes from an updated generator template to an existing scaffolded harness. It compares the current harness against a fresh template render using original variables, identifies added, removed, and changed files, classifies changes as clean or conflicting, and optionally applies updates with Git-style conflict markers or rejection files. Use this when the generator version has evolved and you need to sync a harness forward while preserving local edits.

View source Repository: agent-harness-generator

Install in Claude Code

Copy

git clone --depth 1 https://github.com/ruvnet/agent-harness-generator /tmp/upgrade-harness && cp -r /tmp/upgrade-harness/.claude-plugin/skills/upgrade-harness ~/.claude/skills/upgrade-harness

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# upgrade-harness

> Codex skill: drift detection + apply for a scaffolded harness.

## What it does

Re-renders the template that produced the harness against the current generator version, using the same `vars` the original scaffold used. Computes a 3-bucket plan:

| Bucket | Meaning |
|---|---|
| **added** | upstream template now has files the harness doesn't |
| **removed** | upstream template no longer has files the harness does |
| **changed** | upstream and harness differ; sub-classified `clean` vs `conflict` |

A **clean** change means the harness's version equals the original generation — apply safely. A **conflict** means the user edited the file post-scaffold; the apply step writes either Git-style inline markers or a `.rej` sidecar for manual merge.

## Usage from Codex

```
/upgrade-harness                                       # dry-run on cwd
/upgrade-harness path=./my-harness
/upgrade-harness path=./my-harness apply=true
/upgrade-harness path=./my-harness apply=true conflict=rej
```

## Equivalent CLI

```bash
harness upgrade ./my-harness                           # dry-run
harness upgrade ./my-harness --apply                   # apply, inline conflicts
harness upgrade ./my-harness --apply --conflict=rej    # apply, .rej sidecars
```

## Lifecycle position

```
scaffold (create-agent-harness)
    ↓
 edit (you)
    ↓
 upgrade (this skill)   <- catches up to the latest template
    ↓
 sign / verify / publish
```

## Exit codes

| Code | Meaning |
|---|---|
| 0 | No drift OR clean apply (no conflicts) |
| 1 | Unresolved conflicts after apply, OR not a generated harness, OR template missing |
| 2 | Bad `--conflict=` value |

CI workflows can gate on exit 1 to flag unresolved conflicts.