ctx-upgrade

Update the context-mode plugin from GitHub and restore its build, installation, npm package, and hooks.

2|Updated May 5, 2026
One-click install
npx skills add https://github.com/OrestesK/pi --skill ctx-upgrade-orestesk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ctx-upgrade
Source: https://github.com/OrestesK/pi/tree/main/packages/context-mode/skills/ctx-upgrade
Command: npx skills add https://github.com/OrestesK/pi --skill ctx-upgrade-orestesk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies updating the context-mode plugin from GitHub while ensuring it is rebuilt, reinstalled, and correctly connected to the required hooks and settings.

Core Features & Use Cases

  • Automated Upgrade: Pulls the latest context-mode source and runs the plugin's upgrade workflow.
  • Installation and Configuration: Builds and installs the plugin, updates the global npm package, and configures hooks.
  • Validation and Recovery: Reports versioned results and doctor checks, with a local CLI fallback if the MCP upgrade tool is unavailable.
  • Use Case: Use this Skill when context-mode needs to be upgraded and its installation or hooks must be verified before restarting the session.

Quick Start

Ask the agent to upgrade context-mode, verify the installation and hooks, and report the resulting version and doctor checks.

Frequently Asked Questions about ctx-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade the context-mode plugin from GitHub and restore its hooks?

To upgrade context-mode, the Skill pulls the latest source from GitHub, rebuilds and reinstalls the plugin, updates the global npm package, and restores hook configuration. It then reports versioned results and doctor checks before requiring a session restart.

What is the best way to fix a broken context-mode installation after a failed update?

The best way to fix a broken context-mode installation is to run an automated upgrade workflow that rebuilds the plugin, updates the global npm package, verifies hook configuration, and reports doctor checks to ensure full recovery.

Can I upgrade context-mode if the MCP upgrade tool is unavailable?

Yes, you can upgrade context-mode when the MCP upgrade tool is unavailable by falling back to the plugin's local CLI. This fallback requires shell execution to complete the build, installation, and hook configuration.

Does upgrading context-mode require a session restart to apply changes?

Yes, upgrading context-mode requires a subsequent session restart to apply changes. The upgrade process updates the source, build, global npm package, and hooks, but the new configuration only takes full effect after restarting.

How do I verify context-mode hooks and installation after pulling the latest version?

You verify context-mode hooks and installation by running doctor checks after the upgrade workflow completes. The Skill reports versioned results and validates that the build, global npm package, and hook configuration are correctly connected.