[skill-drift] sentry-node-sdk may need updates for OTLP integration (node-core/light)

[github-actions]

cc @getsentry/team-javascript-sdks

SDK Changes Detected

The following PR was merged to getsentry/sentry-javascript in the last 7 days that may affect the sentry-node-sdk skill:

• feat(node-core): Add OTLP integration for node-core/light sentry-javascript#19729 — feat(node-core): Add OTLP integration for node-core/light (merged 2026-03-30)

Potential Skill Gaps

1. New OTel-First Setup Path: The PR introduces @sentry/node-core/light/otlp — a lightweight integration for users who already manage their own OpenTelemetry setup and want to send trace data to Sentry without adopting the full @sentry/node SDK. New config options: setupOtlpTracesExporter (boolean, default true) and collectorUrl (string, optional custom collector endpoint).

   The sentry-node-sdk skill currently has no OTLP path. By contrast, the Python (sentry-python-sdk) and Ruby (sentry-ruby-sdk) skills both document an OTLP integration path with detection logic (check for existing OTel setup in dependencies) and a separate init pattern. The Node.js skill should similarly document this.

Why This Needs Manual Review

• The OTLP integration uses @sentry/node-core/light/otlp, a sub-package path different from the standard @sentry/node — the skill needs to explain when to prefer this path vs. the full SDK
• The Phase 1 detection step needs new logic to identify OTel-first projects (e.g., @opentelemetry/sdk-node in package.json)
• The Phase 2 recommendation matrix needs a new path that says "OTel tracing detected → use OTLP integration; do not set tracesSampleRate"
• A new setup section analogous to Python's OTLPIntegration or Ruby's config.otlp.enabled is needed
• The sentry-otel-exporter-setup skill's Step 8 currently only lists Python and Ruby — it may need to be updated to include Node.js

Skill Files to Review

• skills/sentry-node-sdk/SKILL.md
• skills/sentry-otel-exporter-setup/SKILL.md (Step 8: Enable trace connectedness)

Priority

MEDIUM — new feature that enables a new integration path for OTel-first Node.js users; no existing functionality broken

Note

🔒 Integrity filter blocked 6 items

The following items were blocked because they don't meet the GitHub integrity level.

• #282 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #20039 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19532 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19810 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7744 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5066 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by SDK Skill Drift Detector · ◷

• expires on Apr 13, 2026, 1:22 PM UTC

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #96

View newer issue

---

This action was performed automatically by the SDK Skill Drift Detector workflow.