ce-update

Compare upstream and installed compound-engineering plugin versions via GitHub CLI.

Updated Sep 25, 2024
One-click install
npx skills add https://github.com/kwam1na/athena --skill ce-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-update
Source: https://github.com/kwam1na/athena/tree/main/.agents/skills/ce-update
Command: npx skills add https://github.com/kwam1na/athena --skill ce-update

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The skill checks whether the compound-engineering plugin installed in Claude Code matches the upstream main version and guides you to update when necessary.

Core Features & Use Cases

  • Probes the upstream and installed versions of the plugin to determine currency.
  • Compares versions and suggests claude plugin update compound-engineering@<marketplace> when older.
  • Handles local development sessions and marketplace-cache layouts to avoid false positives.

Quick Start

Run the ce-update script in Claude Code to verify your plugin is current and apply updates if needed.

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 release?

To check if your Claude Code plugin version matches upstream, the skill probes the installed and upstream versions of the compound-engineering plugin, comparing them to determine if your local deployment is current.

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

The best way to update an outdated compound-engineering plugin is to run the ce-update script, which compares versions and suggests the specific marketplace update command needed to sync your local deployment.

Does the plugin version checker work with both local development sessions and marketplace cache layouts?

Yes, the plugin version checker works with both local Claude Code development sessions and marketplace-cache layouts, accommodating both structures to locate the loaded version and avoid false positives.

Do I need the GitHub CLI to verify my installed Claude Code plugin version?

Yes, you need the GitHub CLI installed and authenticated, as the skill relies on the gh command-line tool to fetch upstream plugin versions and compare them against your local installation.

Why does my plugin update check show a false positive for an outdated version?

A false positive during a plugin update check can occur if the version checker fails to properly handle local development sessions or marketplace-cache layouts, which the skill specifically accommodates to prevent.