Skip to content

feat(skills): route Go projects to the OpenTelemetry AIO variant - #373

Open
marco-g-pm wants to merge 2 commits into
mainfrom
marco/aio-skill-go-otel
Open

feat(skills): route Go projects to the OpenTelemetry AIO variant#373
marco-g-pm wants to merge 2 commits into
mainfrom
marco/aio-skill-go-otel

Conversation

@marco-g-pm

@marco-g-pm marco-g-pm commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Problem

A Go app asking the wizard for AI observability has nowhere to land: the ai-observability skill ships Python and Node variants only, and its decision rules never mention Go. PostHog/posthog-go#306 adds an OTel bridge, making OpenTelemetry the one supported Go path.

for PostHog/posthog-go#306

Changes

  • A go.mod project now routes to the new opentelemetry-go variant first, before the framework and provider rules (new rule 1 in 1-begin.md).
  • Adds the opentelemetry-go variant to config.yaml, pointing at the OpenTelemetry install doc and the Go library doc.
  • The install and instrument references each gain one Go paragraph: declare the bridge module in go.mod, hand-author the gen_ai.* spans, same cardinality rules.
  • Mechanical: variant count 68 to 69 in two files, rules 1 to 4 renumbered 2 to 5.

Testing

Release notes

Merge wants mcp-publish plus minor so the variant reaches users. The install doc it points at gains its Go tabs in a posthog monorepo PR that should land first.

🤖 Agent context

Written by Claude Code from the Slack thread on posthog-go#306 (https://posthog.slack.com/archives/C087XQ7K9K7/p1788170266901319), with the user directing scope. Skills invoked: writing-pr-descriptions, writing-user-facing-copy.

Go has no PostHog wrapper SDK; PostHog/posthog-go#306 adds an OTel
bridge instead. Add the opentelemetry-go variant and make a go.mod
project take it first, before the framework and provider rules.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@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 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/groq
  • /wizard-ci ai-observability/manual-capture
Show more apps
  • /wizard-ci ai-observability/openai
  • /wizard-ci ai-observability/openai-agents
  • /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 mcp-analytics/custom-dispatcher
  • /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.

@carlos-marchal-ph
carlos-marchal-ph requested a review from a team as a code owner September 1, 2026 16:35
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