Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Sentry Error Monitoring Setup and Audit for Any Stack

    1

    Set up or audit Sentry: official SDK, releases, CI source maps, PII and replay privacy, noise filters, throttled alerts, ownership, test error. Verdict MONITORED / NOISY / BLIND.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Sentry Error Monitoring Setup and Audit for Any Stack

    Sentry Error Monitoring Setup and Audit for Any Stack

    Example session with this skill installed

    Audit our Sentry setup. We have a Vite React frontend and an Express API, both on @sentry v11, deployed with GitHub Actions. Stack traces in Sentry are minified and the team muted the alerts channel.

    • Read your context and instructions
    • Compiled the sentry error monitoring

    Sentry setup: shop-web + shop-api — NOISY

    Defaults used: SaaS, user ID only, errors-only replay, traces 0.1 in prod, alerts to #shop-alerts, GitHub Actions.
    SDK: @sentry/react and @sentry/node 11.x (verified against docs.sentry.io today; v11 privacy defaults apply).

    Findings

    #AreaStatusEvidenceFix
    1Source mapsMissingvite.config.ts has no Sentry pluginAdd @sentry/vite-plugin, sourcemap: "hidden"
    2Release tagMissingsrc/sentry.ts:4 no releaseUse git SHA from CI
    3PIIOver-collectingdataCollection unset on v11Set userInfo: false, cookies: false
    4User contextEmail sentsrc/auth.ts:31 setUser({ email })Send { id } only
    5NoiseHighNo denyUrls for extensionsAdd extension filters
    6AlertsSpamThrottling = every trigger60 min, production only
    7API serverOKinstrument.mjs loaded with --importnone

    Changes

    // vite.config.ts
    build: { sourcemap: "hidden" },
    plugins: [react(), sentryVitePlugin({
      org: "acme", project: "shop-web",
      authToken: process.env.SENTRY_AUTH_TOKEN,
      sourcemaps: { filesToDeleteAfterUpload: ["./**/*.map"] },
    })],
    
    // src/sentry.ts
    release: import.meta.env.VITE_SENTRY_RELEASE,
    environment: import.meta.env.MODE,
    dataCollection: { userInfo: false, cookies: false, httpBodies: [] },
    denyUrls: [/^chrome(-extension)?:\/\//i, /^moz-extension:\/\//i],
    

    CI (GitHub Actions)

    env:
      SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
      VITE_SENTRY_RELEASE: ${{ github.sha }}
    - run: npx sentry-cli releases new "$VITE_SENTRY_RELEASE"
    - run: npx sentry-cli releases set-commits --auto "$VITE_SENTRY_RELEASE"
    

    Alerts (proposed, not created)

    AlertTriggerThrottling
    New issueA new issue is created, priority >= high60 min
    RegressionA resolved issue regresses60 min
    SpikeAn issue escalates30 min

    Ownership: path:src/checkout/** #payments, path:api/** #backend.

    Verification

    Not yet run. After deploy to staging, open the temporary /debug-sentry route and confirm: original file:line in trace, release = commit SHA, no email in event JSON.

    Open items

    • Rotate nothing: no committed token found.
    • Re-run audit after fixes; expected verdict MONITORED if the test error checks pass.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Most Sentry installs work on day one and quietly decay. Stack traces stay minified because source maps never uploaded, every event says release unknown, extension errors drown real bugs, alerts fire on every event, and user emails and IPs end up in event payloads. The JavaScript SDK v11 also changed privacy defaults, so an unset option now collects more than it used to.

    This skill has your coding agent set up or audit Sentry the way the current docs describe:

    • Detects the stack (Next.js, React, Vue, Node/Express, Python/Django/FastAPI, Go, React Native, Flutter) and the installed SDK version
    • Uses the official wizard or SDK install path and reviews what the wizard changed
    • Sets release and environment consistently between the SDK and the upload step
    • Uploads source maps or debug symbols from CI with bundler plugins or sentry-cli, and keeps maps off your public server
    • Sets sampling (keep all errors, sample traces, drop health checks), errors-only Session Replay with masking on, and explicit PII settings (dataCollection or send_default_pii)
    • Adds noise filters for browser extensions and known benign errors
    • Proposes new issue, regression and spike alerts with throttling, ownership rules, CODEOWNERS and suspect commits
    • Keeps the auth token in CI secrets and checks the repo for committed tokens
    • Proves the pipeline with a test error and a checklist

    Who it is for: developers and small teams adding Sentry, fixing unreadable traces, or cutting alert noise before a launch.

    Honesty note: the skill tells the agent to verify SDK options and versions on docs.sentry.io before writing config, to label anything unverified, and not to claim the setup works until a test event is seen. It proposes alert and project changes but does not apply them without your approval.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    The skill works from your code and CI config; it cannot read your Sentry organization settings unless you provide them. Alert and ownership changes are proposed, not applied. SDK defaults change between versions, so results depend on verifying the docs for your platform. Plan-gated features such as code owners import need a Business or Enterprise plan.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    Accounts
    Sentry accountSentry auth token
    Software
    Sentry SDK@sentry/wizardNode.jsPython

    SaaS or self-hosted Sentry works; have your project DSN ready. The SDK is installed only after you approve. Store the auth token as a CI secret for source map upload.

    Permissions

    Terminal / Shell
    Write Files
    Environment Variables
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    SKILL.md with the workflow, verdict and output template, and references/sentry-facts.md with the SDK options, defaults, commands, alert and ownership facts it relies on, dated October 2026 with source links.

    Any agent that reads SKILL.md skills, such as Claude Code, Codex CLI, Cursor, VS Code Copilot and Gemini CLI.

    Unzip the folder into your agent's skills directory and ask it to set up or audit Sentry. You need a Sentry account (SaaS or self-hosted) and, for uploads, an auth token stored as a CI secret.

    It cannot see your Sentry project settings unless you share them or grant access, it proposes alerts rather than creating them, and SDK options change, so it relies on checking the docs when web access is available. It is not a replacement for a full OpenTelemetry tracing setup.

    It works from a checked list of current facts, including the v11 privacy default change, a fixed audit order, a three-state verdict, and an end-to-end test step, so the agent is less likely to use outdated options or skip source maps, PII and alert throttling.

    It changes your code and CI. For settings that live in the Sentry web app, such as alert rules, ownership rules, inbound filters and issue grouping, it writes the exact settings to apply and you click them in. It does not log in to your Sentry account.

    New in DevOps & Cloud