Skip to content

ci(release): stop pushing omnibus skills into PostHog/ai-plugin - #527

Open
JakeRuth wants to merge 1 commit into
mainfrom
jake/drop-ai-plugin-skill-push
Open

JakeRuth wants to merge 1 commit into
mainfrom
jake/drop-ai-plugin-skill-push

Conversation

@JakeRuth

@JakeRuth JakeRuth commented Nov 13, 2026 •

Copy link
Copy Markdown

Problem

  • PostHog is removing the bundled skills from its AI plugin (feat: ship the plugin with no bundled skills ai-plugin#311), so plugin users load skills from the MCP server instead.
  • The release workflow here has two steps that copy the omnibus skills into PostHog/ai-plugin. They are dead code today.
  • In the last 80 runs of this workflow, back to July 15, neither step ran once. In the runs checked, "Commit plugins to skills repo" fails first, so both steps are skipped (example).
  • ai-plugin gets these skills another way: its own daily sync downloads the release.
  • If the failing step is fixed (fix(release): mirror the skills repo by PR instead of the commit API #365 changes it), these two steps would start to write skills back into ai-plugin.

Order of the whole change: PostHog/posthog#135733 → PostHog/posthog#135734 → flag fully on → PostHog/ai-plugin#311 together with #527, PostHog/posthog#135736 and PostHog/posthog.com#22349.

Changes

  • Removes the two ai-plugin steps.
  • Narrows the mirror app token to the skills repo.
  • Updates the comments and the README that name ai-plugin as a downstream mirror. That part is mechanical.

What does not change

Release assets are untouched, so nothing that downloads a release is affected:

  • The wizard.
  • The PostHog MCP server, which loads skills-mcp-resources.zip.
  • The PostHog/skills sync.
  • The builds in PostHog/posthog that download the release (agent harness, desktop app, Tasks sandbox image).
  • ai-plugin's own daily sync.

The PostHog/skills mirror step, the Slack notice and the S3 mirror in this workflow also stay as they are.

Note

Merge this together with PostHog/ai-plugin#311 or after it. The README line about ai-plugin only becomes true once ai-plugin drops its bundle.

How did you test this code?

  • Not run: the release workflow and the test suite. The only test file change is one comment.
  • Wizard CI not run. This PR does not change the skills or any release asset the wizard downloads.
  • Checked: no remaining step references the removed step ids or the .ai-plugin-push directory.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Agent: Claude Code, Claude Opus 5.5 (code), Claude Fable 5.2 (description)

🤖 Generated with Claude Code

The ai-plugin is moving to ship no bundled skills; agents get skills from
the MCP server's `learn` command instead. Remove the release steps that
copy the omnibus skills into ai-plugin's skills/ directory, narrow the
mirror app token to the skills repo, and update comments and the README
that describe ai-plugin as a downstream mirror.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JakeRuth JakeRuth self-assigned this Nov 13, 2026
@github-actions

Copy link
Copy Markdown

🧙 Wizard CI

Run the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands:

Test all apps:

  • /wizard-ci all

Test all apps in a directory:

  • /wizard-ci ai-observability
  • /wizard-ci basic-integration
  • /wizard-ci feature-flags
  • /wizard-ci mcp-analytics
  • /wizard-ci replay-vision
  • /wizard-ci revenue
  • /wizard-ci self-driving
  • /wizard-ci warehouse
  • /wizard-ci warehouse-seeded

Test an individual app:

  • /wizard-ci ai-observability/anthropic
  • /wizard-ci ai-observability/google-adk
  • /wizard-ci ai-observability/groq
Show more apps
  • /wizard-ci ai-observability/manual-capture
  • /wizard-ci ai-observability/openai
  • /wizard-ci ai-observability/openai-agents
  • /wizard-ci ai-observability/opentelemetry
  • /wizard-ci ai-observability/vercel-ai
  • /wizard-ci basic-integration/android
  • /wizard-ci basic-integration/angular
  • /wizard-ci basic-integration/astro
  • /wizard-ci basic-integration/django
  • /wizard-ci basic-integration/fastapi
  • /wizard-ci basic-integration/flask
  • /wizard-ci basic-integration/flutter
  • /wizard-ci basic-integration/javascript-node
  • /wizard-ci basic-integration/javascript-web
  • /wizard-ci basic-integration/laravel
  • /wizard-ci basic-integration/next-js
  • /wizard-ci basic-integration/nuxt
  • /wizard-ci basic-integration/python
  • /wizard-ci basic-integration/rails
  • /wizard-ci basic-integration/react-native
  • /wizard-ci basic-integration/react-router
  • /wizard-ci basic-integration/sveltekit
  • /wizard-ci basic-integration/swift
  • /wizard-ci basic-integration/tanstack-router
  • /wizard-ci basic-integration/tanstack-start
  • /wizard-ci basic-integration/vue
  • /wizard-ci feature-flags/django
  • /wizard-ci feature-flags/next-js
  • /wizard-ci mcp-analytics/custom-dispatcher
  • /wizard-ci mcp-analytics/go-sdk
  • /wizard-ci mcp-analytics/python-sdk
  • /wizard-ci mcp-analytics/ruby-sdk
  • /wizard-ci mcp-analytics/rust-sdk
  • /wizard-ci mcp-analytics/typescript-sdk
  • /wizard-ci replay-vision/javascript-node
  • /wizard-ci replay-vision/next-js
  • /wizard-ci replay-vision/react-vite
  • /wizard-ci revenue/stripe
  • /wizard-ci self-driving/astro
  • /wizard-ci self-driving/fastapi
  • /wizard-ci self-driving/nuxt
  • /wizard-ci self-driving/react-router
  • /wizard-ci self-driving/sveltekit
  • /wizard-ci warehouse/monorepo-env
  • /wizard-ci warehouse/multi-source-next
  • /wizard-ci warehouse/stripe-node
  • /wizard-ci warehouse/zero-source
  • /wizard-ci warehouse-seeded/next-stripe
  • /wizard-ci warehouse-seeded/next-stripe-declined

Test against a wizard branch:

  • /wizard-ci all wizard:my-branch

Add wizard:<branch> to any command above to pin the wizard branch. It defaults to main.

Results will be posted here when complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants