ce-update

Compare installed compound-engineering plugin version with upstream main HEAD.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill ce-update-xotong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-update
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/compound-engineering/skills/ce-update
Command: npx skills add https://github.com/xotong/claude-marketplace --skill ce-update-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

Verifies that the installed compound-engineering plugin version matches the upstream main HEAD and prompts the user to update when a newer version exists, ensuring consistency and security in Claude Code.

Core Features & Use Cases

  • Version probing: Reads the upstream version from main and compares it to the currently loaded marketplace cache version.
  • Decision guidance: Recommends the exact update command when an update is needed and handles local development cache scenarios gracefully.
  • Platform awareness: Works with Claude Code plugin harness cache layout and reports whether it is running from a standard marketplace installation or a local development environment.

Quick Start

Update the ce-update plugin to the latest marketplace version.

Frequently Asked Questions about ce-update

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

FAQPage Schema
How do I check if my Claude Code plugin version matches the upstream main HEAD?

To check if your Claude Code plugin version matches the upstream main HEAD, it reads the upstream version from main's plugin.json and compares it against the currently loaded marketplace cache version to detect any mismatches.

What is the best way to update a compound-engineering plugin in Claude Code?

The best way to update a compound-engineering plugin is to run the version check, which compares your installed cache version against upstream main and provides a ready-to-run update command when a newer version is detected.

Does the version check work with local development environments or only standard marketplace installs?

The version check works with both standard marketplace installs and local development environments, gracefully handling the Claude Code plugin harness cache layout to report whether it is running from a marketplace installation or local development.

Do I need the gh CLI installed to run plugin version checks?

Yes, you need the gh CLI installed as a dependency to run plugin version checks, because it is required to read the upstream version from main's plugin.json and compare it with the loaded cache version.

Why does my Claude Code session show an outdated compound-engineering plugin version?

Your Claude Code session shows an outdated compound-engineering plugin version because the currently loaded marketplace cache version does not match the upstream main HEAD, triggering a prompt to update using the provided command.