What problem does it solve? Keeping a repo's Ratchet framework files current with upstream releases is risky: a naive copy can clobber locally modified files or overwrite project-owned content like GATES.md, memory/, and plan issues. This Skill performs a manifest-aware, profile-scoped update on a dedicated review branch and stops for human review before anything is committed. ## Core Features & Use Cases - Manifest-aware selection: Reads ratchet-manifest.json at the target ref and pulls only framework-class files matching the profiles recorded in .ratchet-install.json. - Local-modification protection: Compares on-disk content against recorded hashes and skips diverged files by default, with an opt-in --force flag. - Review-first workflow: Creates a ratchet-update/<date> branch, shows git diff --stat, and hands the user commit/push/PR commands without ever committing or merging. - Use Case: A maintainer wants to move their project from Ratchet v5.2 to v5.3 without losing custom tweaks to framework files; the updater refreshes only untouched files and lists the locally modified ones it refused to overwrite. ## Quick Start Ask the agent to update the Ratchet framework in this repo to the latest upstream version on a review branch.
