Skip to content
Development
Skill

/gsd-update

Update GSD to latest version with changelog display

From plugin
gsd-core
8k71 skills34 agents71 commands7 hooks
Install
$ npx -y skills add open-gsd/gsd-core --skill gsd-update --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/gsd-update

Context preview

The summary Claude sees to decide when to auto-load this skill.

Update GSD to latest version with changelog display

SKILL.md

gsd-update.SKILL.md
name: gsd-update
description: "Update GSD to latest version with changelog display"
argument-hint: "[--sync | --reapply | --next | --rc]"
allowed-tools:
  - Read
  - Write
  - Edit
  - Bash
  - Glob
  - Grep
  - AskUserQuestion

<objective> Check for GSD updates, install if available, and display what changed.

Routes to the update workflow which handles:

  • Version detection (local vs global installation)
  • npm version checking
  • Changelog fetching and display
  • User confirmation with clean install warning
  • Update execution and cache clearing
  • Restart reminder

</objective>

<execution_context> @~/.claude/gsd-core/workflows/update.md </execution_context>

<flags>

  • **--sync**: Sync managed GSD skills across runtime roots so multi-runtime users stay aligned after an update. Runs the sync-skills workflow (--from, --to, --dry-run, --apply flags supported).
  • **--reapply**: Reapply local modifications after a GSD update. Uses three-way comparison (pristine baseline, user-modified backup, newly installed version) to merge user customizations back. Runs the reapply-patches workflow.
  • **--next** (alias **--rc**): Target the `@next` RC dist-tag instead of `@latest` so you can install or refresh a release candidate (e.g. `1.4.0-rc.1`) through the normal update flow — scope/runtime detection, changelog preview, custom-file backup, and cache clearing all still apply. Omitting it keeps targeting `@latest` (no change). See ADR #660 for the RC channel.
  • **(no flag)**: Standard update — check for new version, show changelog, install.

</flags>

<process> Parse the first token of $ARGUMENTS:

  • If it is `--sync`: strip the flag, execute the sync-skills workflow (passing remaining args for --from/--to/--dry-run/--apply).
  • If it is `--reapply`: strip the flag, execute the reapply-patches workflow.
  • Otherwise (including `--next` / `--rc`): execute the update workflow end-to-end, passing `$ARGUMENTS` through so the workflow's parse_update_channel step can select the release channel.

</process>

<execution_context_extended> @~/.claude/gsd-core/workflows/sync-skills.md @~/.claude/gsd-core/workflows/reapply-patches.md </execution_context_extended>

Read more
Ships withgsd-core

Git. Ship. Done. A light-weight meta-prompting, context engineering, and spec-driven development system for Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more.

Get the whole plugin