gsd-update

name	gsd-update
description	Update GSD to latest version with changelog display

<cursor_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-update or describes a task matching this skill.
• Treat all user text after the skill mention as {{GSD_ARGS}}.
• If no arguments are present, treat {{GSD_ARGS}} as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

• Present options as a numbered list in your response text
• Ask the user to reply with their choice
• For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Cursor tools when executing GSD workflows:

• Shell for running commands (terminal operations)
• StrReplace for editing existing files
• Read, Write, Glob, Grep, Task, WebSearch, WebFetch, TodoWrite as needed

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use Task(subagent_type="generalPurpose", ...)
• The model parameter maps to Cursor's model options (e.g., "fast") </cursor_skill_adapter>

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

<execution_context> @/Users/diegocaminor/Documents/proyectos/anyone-ai/final-project/AnyoneAIInterviewerBackend/.cursor/get-shit-done/workflows/update.md </execution_context>

**Follow the update workflow** from `@/Users/diegocaminor/Documents/proyectos/anyone-ai/final-project/AnyoneAIInterviewerBackend/.cursor/get-shit-done/workflows/update.md`.

The workflow handles all logic including:

1. Installed version detection (local/global)
2. Latest version checking via npm
3. Version comparison
4. Changelog fetching and extraction
5. Clean install warning display
6. User confirmation
7. Update execution
8. Cache clearing