harness-update_skill

This skill safely updates projects with the latest harness version, performing backups and non-destructive config updates.
  • Shell

212

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill chachamaru127/claude-code-harness --skill harness-update

  • SKILL.md4.0 KB

Overview

This skill safely updates a project's Claude Code harness to the latest harness version with automated backups and non-destructive merges. It preserves user customizations, detects template changes, and proposes safe fixes for breaking-change patterns. Use it when you need controlled harness or template updates while keeping project-specific settings intact.

How this skill works

The skill detects the current harness version from .claude-code-harness-version and compares it to the latest release, then runs a content-level check (template-tracker) to find template updates. It creates a timestamped backup, applies non-destructive updates to settings and workflow files (overwriting only when not localized), fixes known breaking-change patterns, and performs post-update verification with syntax checks and a completion report. Skills diffs are detected and proposed rather than applied blindly.

When to use it

  • User issues the /harness-update command
  • You need to update the harness version or harness templates
  • Template updates are available and you want a safe, reversible apply
  • You want to fix known harness-related configuration issues (permissions, deprecated keys)
  • You need to add new harness features without losing custom settings

Best practices

  • Confirm scope before updating: harness/template updates only, not app or dependency updates
  • Review proposed skill diffs and localization decisions before applying merges
  • Keep incomplete Plans.md tasks and .claude/memory untouched; verify backups first
  • Run template-tracker and JSON syntax checks after the update
  • Use the provided backup path (.claude-code-harness/backups/{timestamp}/) to restore if needed

Example use cases

  • Update a project from an older harness version while preserving custom .claude/settings.json entries
  • Apply template fixes that correct permission syntax or deprecated settings
  • Detect new skills introduced in the harness and propose adding them to the project
  • Merge workflow updates into a localized project with user-confirmed merges
  • Create an automatic backup and verification report after performing harness updates

FAQ

No. Custom settings in .claude/settings.json, incomplete Plans.md tasks, and .claude/memory are preserved and never overwritten by the update.

What happens if templates are localized?

If templates are localized the skill proposes a merge and requests confirmation before merging; if not localized, files may be overwritten.

Can this update app code or dependencies?

No. The skill is limited to harness and template updates and will not perform application or dependency version bumps.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
harness-update skill by chachamaru127/claude-code-harness | VeilStrat