V3.4 rewrites the update mechanism from scratch. Previously, keeping the squad up to date
required a local clone of the repository. Now a single curl installs the
/update-reviewsquad command, and that command handles everything — pulling agents,
commands, templates, and hooks directly from GitHub. No local repo. No manual file copying.
Incremental runs sync only what changed.
-
/update rewritten to use curl
The update command no longer requires a local clone of
Corye-CIC/Review_Squad. It fetches each file individually from the GitHub raw content API using curl. One command, no git setup, no manual file management.
-
One curl to bootstrap
Installing the squad for the first time (or installing the update command on a new machine) is a single curl command that fetches
update-reviewsquad.md to ~/.claude/commands/. From there, /update-reviewsquad handles the full install: all 25 agents, all commands, hooks, and templates.
-
Version tracking via
~/.claude/review-squad-version
The update command writes the current version tag to ~/.claude/review-squad-version after each successful sync. The version file is read on the next run to determine whether an update is available and which files have changed since the last sync.
-
First run syncs all files; incremental runs sync only what changed
On the initial install (no version file present), every agent, command, hook, and template is fetched. On subsequent runs, the command compares the current version to the latest release tag and fetches only the files that differ. This makes incremental updates fast — a patch release that only changes two agents fetches two files, not twenty-five.
-
Custom agents never overwritten
Any agent file prefixed with
custom- is skipped by the update command. Custom agents created via /create-agent (introduced in V3.5) live in ~/.claude/agents/custom-*.md and are never touched by /update-reviewsquad, regardless of what changed in the upstream repo.