skills.rest
Evolutionary-Leadership
Evolutionary-LeadershipOFFICIAL
Explore all skills by this author →
GitHub

harness-upgrade

Upgrade harness workflows, skills, and hooks to a target version against the published template repo.

Updated Aug 13, 2026
Search Tags:#automation#git#ci/cd#versioning#claude code#github actions#upgrade
One-click install
npx skills add https://github.com/Evolutionary-Leadership/harness --skill harness-upgrade-evolutionary-leadership
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-upgrade
Source: https://github.com/Evolutionary-Leadership/harness/tree/main/.claude/skills/harness-upgrade
Command: npx skills add https://github.com/Evolutionary-Leadership/harness --skill harness-upgrade-evolutionary-leadership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a repository's harness infrastructure (GitHub workflows, Claude Code skills, hooks, settings) current is error-prone: manual upgrades miss breaking changes, overwrite project-specific config, or silently leave retired files behind. This Skill plans and applies a versioned upgrade by comparing your repo against tagged snapshots of the published template repo. ## Core Features & Use Cases - Tree-based upgrade planning: Clones the target and installed version tags and runs a planner script that classifies every path as update, create, delete, merge, write-once, or blocked. - Release-note narrative: Reads per-version release notes from the cloned tree and surfaces Breaking items above the confirmation prompt before anything is applied. - Safe application and verification: Merges config without dropping project keys, never overwrites CLAUDE.md, re-runs the planner to verify copies landed, and only then stamps the new version in .harness-version. - Use Case: Your repo is stamped at harness version 0.7.5 and 0.7.7 is published. Run the upgrade to see what changed, review breaking items, approve the file plan, and get a verified, reviewable commit. ## Quick Start Run /harness-upgrade to plan and apply an upgrade of this repository's harness infrastructure to the latest published version.

Frequently Asked Questions about harness-upgrade

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

FAQPage Schema
How do I upgrade harness workflows and skills to a newer version?▼

Run /harness-upgrade, optionally with a target version like 0.7.7. It reads your .harness-version stamp, clones the target tag from the published template repo, builds a file plan, shows breaking changes, and applies only what you confirm.

How does the upgrade avoid overwriting my project configuration?▼

Config files like .claude/settings.json and railway.json are merged, never copied over: the upgrade only adds keys the project lacks and never changes values the project already set. CLAUDE.md is never overwritten; additions are only suggested.

Does the harness upgrade work offline or behind a proxy?▼

Yes. Version discovery uses git ls-remote and trees come from git clone, with release notes read from the cloned tree itself. No GitHub API calls are made, so it works in sandboxes and behind proxies that block the API.

What happens if the upgrade cannot read the release notes?▼

The upgrade shows a BREAKING COULD NOT BE READ banner above the confirmation prompt, explaining that breaking changes cannot be listed and pointing you to the releases page in a browser. You may still apply, but never without being told the list is missing.

Why does the upgrade stop with a hazard about check:spec?▼

A non-empty hazards list stops the upgrade before anything is applied. The spec-loop-armed-without-product hazard means your spec anchor gate silently passes without enforcing, which must be fixed or explicitly accepted before continuing.

Can the upgrade delete files, and is it reversible?▼

Deletions are proposed only for retired files in trees the harness owns, and only when your installed version has a tag to compare against. Deletions are always confirmed separately since re-running the upgrade cannot undo a removal.

Related Skills

Explore More Software Engineering Skills→
RCSnyderRCSnyder

init

Scaffold the Lights Out SWE harness into a target Git repository.

Community
Basic
moltis-orgmoltis-org
2.8k

requesting-code-review

Run static security scans, baseline quality gates, and auto-fix loops before git commits.

Official
Advanced
adaptive-enforcement-labadaptive-enforcement-lab
3

phase-1-foundation-weeks-1-4

Enforce pre-commit secrets checks and branch protection across repositories.

Official
Intermediate
ChinchillaEnterprisesChinchillaEnterprises

skills-sync

Synchronize local Claude Code skills with the ChillSkills GitHub repository.

Official
Basic