ce-update
Best for Claude Code usersWorks with GitHubLow risk
⌘source
- author
@EveryInc- language
- TypeScript
★15kstars
1.2kforks
Apr 21, 2026
✦overview.md
Key Features
- ·Checks compound-engineering plugin version against latest release
- ·Fixes stale marketplace/cache state if outdated
- ·Works exclusively in Claude Code environment
- ·Uses pre-resolved context for validation
- ·Triggers on specific user update/check phrases
Use Cases
- →When a user reports issues that might stem from a stale compound-engineering plugin version
- →When a user explicitly requests to update or check the compound-engineering plugin version
- →During routine maintenance to ensure plugin cache is current
- →When troubleshooting plugin-related problems in Claude Code
Best for
- ✓Claude Code users
- ✓Compound-engineering plugin maintainers
- ✓Troubleshooting sessions
Not ideal for
- !Non-Claude Code environments
- !Other plugins or tools
- !General version checking
FAQs
name
ce-update
description
Check if the compound-engineering plugin is up to date and fix stale cache if not.
Use when the user says "update compound engineering", "check compound engineering version",
"ce update", "is compound engineering up to date", "update ce plugin", or reports issues
that might stem from a stale compound-engineering plugin version. This skill only works
in Claude Code — it relies on the plugin harness cache layout.
disable-model-invocation:true
ce_platforms:["claude"]
Check & Fix Plugin Version
Verify the installed compound-engineering plugin version matches the latest released version, and fix stale marketplace/cache state if it doesn't. Claude Code only.
Pre-resolved context
The three sections below contain pre-resolved data. Only the Plugin root
path determines whether this session is Claude Code — if it contains an error
sentinel, an empty value, or a literal ${CLAUDE_PLUGIN_ROOT} string, tell the
user this skill only works in Claude Code and stop. The other two sections may
contain error sentinels even in valid Claude Code sessions; the decision logic
below handles those cases.
Plugin root path:
!echo "${CLAUDE_PLUGIN_ROOT}" 2>/dev/null || echo '__CE_UPDATE_ROOT_FAILED__'
Latest released version:
!gh release list --repo EveryInc/compound-engineering-plugin --limit 30 --json tagName --jq '[.[] | select(.tagName | startswith("compound-engineering-v"))][0].tagName | sub("compound-engineering-v";"")' 2>/dev/null || echo '__CE_UPDATE_VERSION_FAILED__'
Cached version folder(s):
!ls "${CLAUDE_PLUGIN_ROOT}/cache/compound-engineering-plugin/compound-engineering/" 2>/dev/null || echo '__CE_UPDATE_CACHE_FAILED__'
$install
1-click copynpx skills add EveryInc/compound-engineering-plugin --skill ce-updateSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.