update
Update AIWG to the latest stable version and re-deploy all installed frameworks from the registry
What this skill does
# AIWG Update You update AIWG to the latest stable version and re-deploy all installed frameworks from the registry. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "refresh frameworks" → run `aiwg update` - "redeploy everything" → run `aiwg update --all` - "get the latest aiwg" → run `aiwg update` - "reinstall my frameworks" → run `aiwg update --skip-check` - "what would update change" → run `aiwg update --dry-run` ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Update request | "update aiwg" / "upgrade aiwg" | Run `aiwg update` | | Refresh request | "refresh frameworks" | Run `aiwg update` | | Full redeploy | "redeploy everything" | Run `aiwg update --all` | | Dry run | "what would update change" | Run `aiwg update --dry-run` | | Provider-scoped | "update for copilot" | Run `aiwg update --provider copilot` | | Skip version check | "just redeploy my frameworks" | Run `aiwg update --skip-check` | ## Behavior When triggered: 1. **Extract intent**: - Should this update everything (`--all`) or only the currently installed frameworks (default)? - Is a specific provider mentioned? - Is this a preview only (`--dry-run`) or should changes be applied? - Is the user asking to redeploy without updating the package (`--skip-check`)? 2. **Run the appropriate command**: ```bash # Default: check for updates + re-deploy installed frameworks aiwg update # Re-deploy all frameworks (equivalent to `aiwg use all`) aiwg update --all # Preview what would be updated (no changes) aiwg update --dry-run # Re-deploy to a specific provider aiwg update --provider copilot # Skip version check, only re-deploy aiwg update --skip-check # Combine flags aiwg update --all --provider cursor ``` Execution sequence: 1. Check npm/git for a newer version (unless `--skip-check`) 2. Read `.aiwg/frameworks/registry.json` to find installed frameworks 3. Re-deploy each installed framework via `aiwg use <framework> [--provider <name>]` 4. Print update summary with per-framework pass/fail status 3. **Report the result** — state which frameworks were updated and whether the package version changed. Flag any deployment failures with remediation (usually `aiwg doctor`). ## Difference from `aiwg sync` `aiwg update` and `aiwg sync` overlap but serve different intents: | | `aiwg update` | `aiwg sync` | |---|---|---| | Target channel | Stable only (default) | Follows configured channel | | Scope | Installed frameworks only (default) | All deployed frameworks | | Typical use | "Get the latest stable release" | "Keep this session current" | Use `aiwg update` when bumping to a new stable release. Use `aiwg sync` during active development sessions to stay current with the configured channel. ## Examples ### Example 1: Standard update **User**: "Update AIWG" **Extraction**: Standard update, no flags **Action**: ```bash aiwg update ``` **Response**: "Updated AIWG 2026.3.12 → 2026.3.15. Re-deployed sdlc-complete and media-marketing-kit to claude-code. Both frameworks updated successfully." ### Example 2: Dry run preview **User**: "What would `aiwg update` change?" **Extraction**: Preview requested, no changes **Action**: ```bash aiwg update --dry-run ``` **Response**: "Dry run: would update from v2026.3.12 to v2026.3.15 and re-deploy the following frameworks: sdlc-complete, media-marketing-kit." ### Example 3: Full redeploy to a provider **User**: "Redeploy all frameworks to Cursor" **Extraction**: Full redeploy (`--all`), provider = cursor **Action**: ```bash aiwg update --all --provider cursor ``` **Response**: "Re-deployed all frameworks to cursor: sdlc-complete, media-marketing-kit, research-complete. Artifacts written to `.cursor/agents/`, `.cursor/commands/`, `.cursor/rules/`." ### Example 4: Redeploy without version check **User**: "Just reinstall my frameworks — don't check for updates" **Extraction**: Skip npm check, only redeploy installed frameworks **Action**: ```bash aiwg update --skip-check ``` **Response**: "Skipped version check. Re-deployed sdlc-complete to claude-code. 1/1 frameworks updated." ### Example 5: No frameworks installed **User**: "Update AIWG" **Extraction**: Standard update, but registry is empty or missing **Action**: ```bash aiwg update ``` **Response**: "No frameworks found in `.aiwg/frameworks/registry.json`. To deploy a framework first, run `aiwg use sdlc` or `aiwg use all`." ## Clarification Prompts If the request is ambiguous between update and sync: - "Would you like to update to the latest stable release (`aiwg update`) or sync the current session to your configured channel (`aiwg sync`)?" ## References - @$AIWG_ROOT/src/cli/handlers/utilities.ts — Update command handler (updateHandler) - @$AIWG_ROOT/src/update/checker.mjs — npm/git update check logic - @$AIWG_ROOT/docs/cli-reference.md — CLI reference
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.