sentry-debug-bundle
Collect diagnostic information for Sentry troubleshooting and support tickets. Use when events are not appearing in Sentry, SDK initialization seems broken, DSN connectivity fails, source maps are not resolving, or preparing a support request. Trigger with "sentry debug info", "sentry diagnostics", "debug bundle", "sentry support ticket". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill sentry-debug-bundle --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Collect diagnostic information for Sentry troubleshooting and support tickets. Use when events are not appearing in Sentry, SDK initialization seems broken, DSN connectivity fails, source maps are not resolving, or preparing a support request. Trigger with "sentry debug info", "sentry diagnostics", "debug bundle", "sentry support ticket".
How it works
The skill guides the agent through gathering SDK package versions, verifying the runtime configuration for Node.js and Python SDKs, and extracting options such as DSN presence, environment, release, and integration list. It provides concrete commands and code snippets for:
- Checking installed Sentry packages in Node.js and Python.
- Extracting runtime configuration in Node.js (getting client options and computed diagnostics).
- Extracting runtime configuration in Python (inspecting the current client and options).
- Verifying DSN connectivity and Sentry service status via curl, dig/nslookup, and status endpoints.
- Testing event capture via sentry-cli and programmatic SDK usage (Node.js and Python examples).
- Generating a Markdown debug bundle report containing environment, network checks, service status, and sample artifacts.
- Providing an error handling section that maps common failures to explicit messages and remedies.
When to use it
Use when events are not appearing, SDK initialization is broken, DSN connectivity fails, source maps are not resolving, or preparing a support request. Trigger phrases are provided for initiating the process.
What it can touch
The skill documents commands and snippets that touch:
- Node.js Sentry packages: @sentry/node, @sentry/browser, @sentry/react, @sentry/cli, etc.
- Python sentry-sdk and Hub integration.
- NPM and Python package inspection commands, curl, dig/nslookup, and sentry-cli.
- Environment variables such as SENTRY_DSN, SENTRY_AUTH_TOKEN, and related Sentry project metadata.
Caveats
License is MIT. Prerequisites include at least one Sentry SDK installed and DSN configuration. The steps assume access to Sentry endpoints and, for some checks, a valid SENTRY_AUTH_TOKEN. The guide notes potential failures like beforeSend behavior and network/proxy restrictions, and suggests explicit flush usage to avoid missing delivery.
# Sentry Debug Bundle ## Overview Collect SDK versions, configuration state, network connectivity, and event delivery status into a single diagnostic report. Attach the output to Sentry support tickets or use it to systematically isolate why events are not reaching the dashboard. ## Current State !`node --version 2>/dev/null || echo 'Node.js not found'` !`python3 --version 2>/dev/null || echo 'Pyt
What does the sentry-debug-bundle skill do?
Collect diagnostic information for Sentry troubleshooting and support tickets. Use when events are not appearing in Sentry, SDK initialization seems broken, DSN connectivity fails, source maps are not resolving, or preparing a support request. Trigger with "sentry debug info", "sentry diagnostics", "debug bundle", "sentry support ticket". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill sentry-debug-bundle --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.