Agent Context Update

Update Agent-Context

Update shared Agent-Context files to the latest version without touching project-owned content.

Examples

# Update to latest version
/agent-context-update

# Update to a specific version
/agent-context-update v0.3.0

Prerequisites Check

Before starting, verify Agent-Context is installed:

cat .agent-context/.agent-context-version 2>/dev/null

• If the file does not exist: STOP. Tell the user Agent-Context is not initialized and suggest using the init skill instead.
• If the file exists: note the current version and proceed.

Update

Resolve the target release tag first, then fetch the setup prompt pinned to that tag and follow its instructions. Fetching a specific release tag (never the mutable main branch) is deliberate: the tag is pinned for the whole run, so the fetched prompt is fixed between resolution and execution, and it changes only when a new release is published — unlike main, which every push mutates. (Full tamper-resistance additionally requires tag/release protection on the source repo.)

# Resolve target version: explicit $ARGUMENTS, else latest release (never mutable `main`)
TAG="${ARGUMENTS:-$(gh api repos/lx-wnk/Agent-Context/releases/latest --jq .tag_name)}"
curl -fsSL "https://raw.githubusercontent.com/lx-wnk/Agent-Context/${TAG}/.prompts/setup-prompt.md"

The setup prompt auto-detects UPDATE mode (because .agent-context-version exists). Follow the fetched instructions, subject to the consent gates in Trust Boundary & Consent below. The setup prompt handles:

1. Version check — fetch latest release, compare with current version
2. Shared file refresh — overwrite only shared files (agent-startup.md, layer0-agent-workflow.md, base-principles.md, plugins.json)
3. New templates — create any new template files introduced in the new version (without overwriting existing ones)
4. Agent sync — update shared agents where they already exist
5. Plugin sync — merge new plugins into .claude/settings.json
6. Compatibility check — scan for deprecated patterns and suggest fixes

If $ARGUMENTS contains a version tag, use that version instead of latest.

Trust Boundary & Consent

This skill fetches a remote setup prompt (pinned to a release tag, see above) and follows it. That prompt performs trust-expanding operations: it can update transitive agents, merge plugins, and modify .claude/settings.json. Treat these as privileged, even though this is an update into an already-initialized project.

Before any step that updates agents (4), merges plugins (5), or writes to .claude/settings.json, stop and get explicit user confirmation — since this merges into an existing configuration, list exactly what will be ADDED or CHANGED against the current state, then wait for a yes. Never install transitive agents or merge plugins silently. If the user declines a step, skip it and continue with the rest of the update.

What is NEVER touched

• AGENTS.md, layer1-bootstrap.md, layer2-project-core.md, layer3-guidebook.md
• All files in memory/ and skills/
• decisions.json
• .claude/settings.json (only additive merges)

After Update

Report:

• Previous version → new version
• Files updated
• Any new templates created
• Compatibility warnings (if any)