
Ctx Upgrade
- 840 installs
- 19.6k repo stars
- Updated August 4, 2026
- mksglu/context-mode
ctx-upgrade is a Claude Code skill that updates the context-mode plugin from GitHub, rebuilds binaries, reinstalls npm globals, and reconfigures hooks for developers who need the latest context-mode release without manua
About
ctx-upgrade is an AI & Agent Building skill from mksglu/context-mode that automates upgrading the context-mode plugin end to end. Triggered via /context-mode:ctx-upgrade, the skill calls the ctx_upgrade MCP tool, runs the returned shell command, and reports a checklist covering GitHub pull, build and install (for example v1.0.39), hook configuration, and doctor checks. Developers reach for ctx-upgrade when context-mode hooks break after an update, npm global binaries drift, or the plugin lags the latest GitHub release. The workflow is intentionally narrow: pull, build, install, configure—no feature authoring.
- Pulls latest context-mode from GitHub
- Builds, installs, and updates the npm global package
- Automatically configures hooks and runs doctor checks
- Outputs a clear markdown checklist with actual version numbers
- Requires session restart after successful upgrade
Ctx Upgrade by the numbers
- 840 all-time installs (skills.sh)
- +95 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #1,289 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mksglu/context-mode --skill ctx-upgradeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 840 |
|---|---|
| repo stars | ★ 19.6k |
| Last updated | August 4, 2026 |
| Repository | mksglu/context-mode ↗ |
How do you upgrade context-mode plugin and hooks?
Keep their context-mode plugin current with the latest GitHub updates, rebuilt binaries, and configured hooks.
Who is it for?
Developers running context-mode who need a repeatable GitHub pull, build, install, and hook repair cycle.
Skip if: Teams not using context-mode or developers authoring new context-mode features instead of upgrading an existing install.
When should I use this skill?
User mentions context-mode upgrade, outdated hooks, ctx_upgrade MCP tool, or /context-mode:ctx-upgrade.
What you get
Updated context-mode binaries, npm global install, reconfigured hooks, and doctor checklist results
- Upgraded context-mode binary
- Configured hooks
- Upgrade checklist
By the numbers
- Documents example install version v1.0.39 in upgrade checklist output
Files
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 PASSUse [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" upgradeRelated skills
FAQ
How does ctx-upgrade update context-mode?
ctx-upgrade calls the ctx_upgrade MCP tool, runs the returned shell command, and verifies pull, build, install, and hook steps. The skill documents checklist output including version labels such as v1.0.39 and doctor pass status.
When should developers run ctx-upgrade?
Developers should run ctx-upgrade when context-mode hooks fail, binaries are stale, or the plugin lags GitHub. The skill is user-invocable via /context-mode:ctx-upgrade for one-command maintenance.