updating-harnesslisted

Use to install or update the Claude Harness in the CURRENT project from its source repo — the source URL is baked in, the operator never pastes it. Detects install-vs-update, pins to the latest GitHub release tag, reports what changed, and re-vendors via vendor-core without clobbering project memory/kaizen/settings. Call it in any repo to onboard or sync the harness after a new release.
orobsonn/claude-harness · ★ 1 · AI & Automation · score 67

Install: claude install-skill orobsonn/claude-harness

# Updating-Harness — install or update the harness from its source repo This skill is the **one-call shortcut** for keeping a project's vendored harness in sync. The operator just invokes it in the repo; the source URL lives here, so there is no URL to copy/paste. It does not plan, implement, or review — it vendors the framework `core/` into all project runtime shells: Claude Code (`.claude/`), OpenCode (`.opencode/`), Codex (`.codex/`) and the pinned Pi launcher (`.pi/harness/`). **One operation:** install or synchronize Claude Code, OpenCode, Codex and Pi to the same release by default. Use `all` unless the operator explicitly selects `claude`, `opencode`, `codex`, `pi`, or `both`. **Announce at start (pt-br):** "Atualizando o Claude Harness a partir do repo-fonte." All identifiers/commands stay in English; every message to the operator is **pt-br, product-language**. --- ## Source (baked in — do NOT ask the operator for a URL) ``` SOURCE_URL = https://github.com/orobsonn/claude-harness.git REPO_SLUG = orobsonn/claude-harness ``` If the operator explicitly passes a different source (fork, local clone path for dev), honor it. Otherwise always use `SOURCE_URL`. --- ## Step 1 — Check the latest release ```bash gh release view --repo orobsonn/claude-harness --json tagName,name,body -q '{tag:.tagName, notes:.body}' ``` Read the project's current version if present: ```bash cat .claude/.harness-version 2>/dev/null || echo "harness not installed yet" ``` Report to t