菜单
Check for updates to OpenTelemetry Collector components and dependencies. Use when the user asks about upgrading OTel, checking for new collector versions, or reviewing upstream OpenTelemetry changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | check-otel-updates |
| description | Check for updates to OpenTelemetry Collector components and dependencies. Use when the user asks about upgrading OTel, checking for new collector versions, or reviewing upstream OpenTelemetry changes. |
This skill checks whether newer versions of the OpenTelemetry Collector are available compared to what this project currently uses, then analyzes release notes for breaking changes and relevant new features.
Read builder-config.yaml in the repo root. The current OTel version is in
the dist.version field (e.g. version: 0.146.0). All core and contrib
components should use this same version.
Use gh (GitHub CLI) to check for releases newer than the current version in
both repositories:
# Core collector
gh release list --repo open-telemetry/opentelemetry-collector --limit 10
# Contrib collector
gh release list --repo open-telemetry/opentelemetry-collector-contrib --limit 10
Compare the release tags against the current version. If no newer versions exist, report that the project is up to date and stop.
For every version between the current version (exclusive) and the latest, fetch the release notes:
gh release view <tag> --repo open-telemetry/opentelemetry-collector
gh release view <tag> --repo open-telemetry/opentelemetry-collector-contrib
Read builder-config.yaml in the repo root to get the full list of components.
Each section (exporters, processors, receivers, extensions,
connectors) contains gomod entries whose module path identifies the
component. Extract the component name from each module path (e.g.
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/fileexporter
→ exporter/file).
Only report changes that affect these components or are project-wide /
general changes (tagged all, pkg/confmap, pkg/otelcol, pkg/service,
cmd/builder, etc.). Skip our own custom components under
github.com/observeinc/observe-agent/.
For each new version, produce a report with the following sections:
List every breaking change that affects our components or is project-wide. For each one, explain:
List deprecations relevant to our components with migration guidance.
Briefly list enhancements to our components that may be useful.
List bug fixes for our components, especially any that fix issues we may have encountered.
Note if the minimum Go version requirement changed.
The components/ directory contains custom OTel components, each with its own
go.mod. Find all go.mod files under components/:
find components -name go.mod
For each one, compare the OTel library versions (modules under
go.opentelemetry.io/collector/ and
github.com/open-telemetry/opentelemetry-collector-contrib/) against the
versions in the root go.mod. Flag any that have diverged.
If the target upgrade version differs from the root go.mod, note that both
the root and component go.mod files will need to be updated together.
Based on the analysis:
Add one or more OpenTelemetry Collector components (receivers, processors, exporters, connectors, extensions) to the observe-agent distribution. Use for ALL requests that mention adding, including, or enabling a new OTel component. Triggers: add receiver, add processor, add exporter, add connector, add extension, new OTel component, include component, enable component, add otel, otelcol component.
Release a new version of the Observe Agent. Use when the user asks to release, tag, publish, or cut a new version of the observe-agent, or mentions the release process.
Run a local end-to-end smoke test of the observe-agent to verify it collects and exports telemetry correctly. Use when the user wants to verify their branch changes work, run a smoke test, test the agent locally, or validate the observe-agent pipeline before committing or merging.