PluginBench
Skill
Fail
Audit score 45

ctx-upgrade

mksglu/context-mode

Update context-mode plugin from GitHub and reconfigure hooks/settings.

What is ctx-upgrade?

Pulls the latest context-mode from GitHub, rebuilds, reinstalls globally, and reconfigures hooks. Use this when you need to upgrade to a newer version or fix configuration issues after a manual change.

  • Fetches latest code from GitHub repository
  • Builds and installs the updated plugin
  • Updates npm global installation
  • Configures hooks and settings automatically
  • Runs diagnostic checks to verify installation
  • Returns results as a markdown checklist

How to install ctx-upgrade

npx skills add https://github.com/mksglu/context-mode --skill ctx-upgrade
Prerequisites
  • context-mode plugin already installed
  • Node.js and npm available in PATH
  • Git installed for pulling from GitHub
  • Write access to plugin installation directory
Claude Code
Cursor
Windsurf
Cline

How to use ctx-upgrade

  1. 1.Invoke the skill with /context-mode:ctx-upgrade trigger
  2. 2.Call the ctx_upgrade MCP tool to get the shell command
  3. 3.Execute the returned command in your shell
  4. 4.Review the markdown checklist output for success/failure status
  5. 5.Restart your session to activate the updated version
  6. 6.If MCP tool fails, manually run the fallback command from the plugin root

Use cases

Good for
  • Upgrade context-mode to a newer version when available
  • Fix broken hooks or settings after manual edits
  • Reinstall the plugin after a failed update
  • Verify plugin integrity with built-in doctor checks
  • Refresh configuration after environment changes
Who it's for
  • context-mode plugin users
  • Developers maintaining local context-mode installations
  • Users troubleshooting plugin configuration issues

ctx-upgrade FAQ

What does ctx-upgrade actually do?

It pulls the latest code from GitHub, rebuilds the plugin, updates the global npm installation, reconfigures hooks, and runs diagnostic checks to ensure everything is working correctly.

Do I need to restart after upgrading?

Yes, you must restart your session after the upgrade completes to pick up the new version.

What if the MCP tool call fails?

Use the fallback method: derive the plugin root (go up 2 levels from the skill directory) and run `node <PLUGIN_ROOT>/cli.bundle.mjs upgrade` or `node <PLUGIN_ROOT>/build/cli.js upgrade`.

How do I know if the upgrade succeeded?

The skill displays results as a markdown checklist with [x] for success and [ ] for failure. Run the doctor check to verify all components pass.

Can I upgrade without restarting?

The upgrade completes, but you must restart your session for the new version to take effect in your active environment.

Full instructions (SKILL.md)

Source of truth, from mksglu/context-mode.


name: ctx-upgrade description: | Update context-mode from GitHub and fix hooks/settings. Pulls latest, builds, installs, updates npm global, configures hooks. Trigger: /context-mode:ctx-upgrade user-invocable: true

Context Mode Upgrade

Pull latest from GitHub and reinstall the plugin.

Instructions

  1. Call the ctx_upgrade MCP tool directly. It returns a shell command to execute.
  2. Run the returned command using your shell execution tool (Bash, shell_execute, etc.).
  3. Display results as a markdown checklist:
    ## context-mode upgrade
    - [x] Pulled latest from GitHub
    - [x] Built and installed v1.0.39
    - [x] Hooks configured
    - [x] Doctor: all checks PASS
    
    Use [x] for success, [ ] for failure. Show actual version numbers.
  4. Tell the user to restart their session to pick up the new version.
  5. Fallback (only if MCP tool call fails): Derive the plugin root from this skill's base directory (go up 2 levels — remove /skills/ctx-upgrade), then run with Bash:
    CLI="<PLUGIN_ROOT>/cli.bundle.mjs"; [ ! -f "$CLI" ] && CLI="<PLUGIN_ROOT>/build/cli.js"; node "$CLI" upgrade