Pull the latest GEO-SEO skill updates from the upstream repository. Compares installed files against the latest release, shows what changed, and updates all skills, agents, scripts, and schema templates in place.

GEO SEO Update Skill Purpose Updates the locally installed GEO SEO skills, agents, scripts, and schema templates to the latest version from the upstream repository. Shows a summary of what changed before and after the update. Update Workflow Step 1: Determine Installed Location The GEO SEO toolkit installs to these locations under ~/.claude/ : Component Install Path Main skill ~/.claude/skills/geo/ Sub skills ~/.claude/skills/geo / Agents ~/.claude/agents/geo .md Scripts ~/.claude/skills/geo/scripts/ Schema templates ~/.claude/skills/geo/schema/ Hooks ~/.claude/skills/geo/hooks/ Verify the installation exists by checking for ~/.claude/skills/geo/SKILL.md . If it does not exist, inform the user that GEO SEO is not installed and suggest running the installer instead. Step 2: Clone Latest from Upstream If the clone fails, report the error and stop. Do not modify any installed files. Step 3: Compare Installed vs Latest Before copying files, generate a diff summary so the user knows what will change: 1. For each component directory, compare the installed files against the cloned files using diff recursive brief . 2. Categorise changes as: New files — exist in upstream but not locally Modified files — exist in both but differ Removed files — exist locally but not in upstream (these are NOT deleted automatically) 3. Present the summary to the user. Step 4: Apply Updates Copy files from the cloned repo over the installed locations: Step 5: Update Python Dependencies If requirements.txt exists in the upstream repo and differs from the installed version: Report any failures but do not treat them as fatal. Step 6: Clean Up Step 7: Report Results Present a summary: If there were removed files upstream, list them and suggest the user review whether to delete them manually. Important Notes Never delete locally installed files that no longer exist upstream. The user may have customised them. List them and let the user decide. Never modify ~/.claude/settings.json or ~/.claude/settings.local.json — these are user configuration files, not part of the GEO SEO toolkit. If already up to date (no diff), report that and skip the copy step. Restart notice: Remind the user that skill changes take effect in new Claude Code sessions. They should restart their session to use the updated skills.

geo-update