Agent skill · software engineering · posthog
upgrade-claude-adapter
Sync this fork of @anthropic-ai/claude-agent-acp (packages/agent/src/adapters/claude) with a newer upstream release: bump the claude-agent-sdk / @agentclientprotocol/sdk, port upstream bug fixes and new SDK message handling, preserve the fork's divergences, verify, and update UPSTREAM.md. Use when asked to "upgrade/sync the claude adapter", "bump the agent SDK", or "port upstream claude-agent-acp changes".
Why this skill is useful
Adds specific procedures for syncing a heavily diverged fork of a complex SDK that the AI wouldn't reliably generate on its own.
What it needs
Requires git installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 37,539 stars on the source repository.
What this skill does
Upgrade the Claude ACP adapter (upstream sync) This is a runbook for syncing our fork of @anthropic-ai/claude-agent-acp (the upstream Zed/agentclientprotocol ACP agent) that lives in packages/agent/src/adapters/claude/ with a newer upstream release. The fork is heavily diverged. The job is to port the valuable upstream changes (SDK bumps, bug fixes, new SDK-message handling) while preserving every intentional divergence — not to make the fork identical to upstream. UPSTREAM.md (this directory) is the source of truth for the fork point, last-synced version/commit, the file mapping, the PostHog-only code, and the intentional divergences. Read it first, update it last. This file is a runbook, not an auto-registered slash command. Invoke it by telling Claude to "follow the upgrade skill in the claude adapter dir." Move it to .claude/skills/<name>/SKILL.md if you ever want it runnable as /<name>. Inputs you need before starting 1. Upstream source checkout — a local git clone of github.com/agentclientprotocol/claude-agent-acp. You need its history to diff. If the user hasn't given the path, ask for it (it's usually somewhere like ~/Cloud/claude-agent-acp). Do not guess. 2. This repo — the fork under packages/agent/. Process 0. Orient (read, don't write) Read UPSTREAM.md. Note Last sync (commit + version), the pinned SDK versions, the File Mapping, PostHog-Only Code (Do Not Sync), and Intentional Divergences. In the upstream checkout, list the change set since the last sync and skim the changelog: git -C <upstream> log --oneline <last-sync-sha>..HEAD git -C <upstream> show <upstream>/CHANGELOG.md:CHANGELOG.md (or just read CHANGELOG.md) Confirm the new target version + HEAD sha and the target SDK versions from the upstream package.json. 1. Triage every commit Bucket each commit since the last sync: Port — bug fixes and new feature / SDK-message handling that are not in the PostHog-only list and don't fight a divergence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills posthog/claude