Agent skill · software engineering · jeremylongshore
sentry-policy-guardrails
Enforce organizational governance and policy guardrails for Sentry usage.
Why this skill is useful
Adds a shared npm package for Sentry configuration that enforces PII scrubbing and compliance standards, providing executable code that extends the AI's capabilities.
What it needs
Requires @sentry/node installed locally. Requires sentry account access. About 7k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry Policy Guardrails Overview Organizational governance framework that prevents Sentry configuration drift across multiple services. A shared npm package (@company/sentry-config) wraps Sentry.init() to enforce PII scrubbing, naming conventions, tagging standards, and per-tier trace rate caps. CI checks block policy violations before merge, and a monthly drift audit detects projects that have fallen out of compliance. Prerequisites @sentry/node v8+ installed in target services Internal npm registry available (GitHub Packages, Artifactory, or similar) Team structure and project ownership defined in Sentry SENTRYAUTHTOKEN with org:read and project:read scopes Compliance requirements identified (SOC 2, GDPR, HIPAA) Instructions Step 1 — Build the Shared Configuration Package Create @company/sentry-config that wraps Sentry.init() with non-negotiable defaults. Mandatory PII scrubbing (cannot be bypassed): Governed init with naming validation, tag injection, and tier-based caps: Service usage (two lines to adopt): Step 2 — Enforce Compliance via CI Add a GitHub Actions workflow to every service repository that blocks policy violations. Optional ESLint rule for IDE feedback: Step 3 — Drift Detection and Cost Governance Monthly drift audit across all Sentry projects: Per-team cost quotas (run weekly): Schedule both in CI: Output @company/sentry-config shared package with enforced PII scrubbing, naming validation, and tier-based trace rate caps Mandatory beforeSend chain: headers, credit cards, emails, and SSNs scrubbed before any custom logic Naming standards enforced at init: release format, validated environments, kebab-case service names Required tags injected: service, team, tier, deployment, region CI workflow blocking hardcoded DSNs, PII collection, and direct Sentry.init() calls Monthly drift audit checking data scrubber, IP scrubbing, sensitive fields, and naming compliance Per-team cost quota enforcement with weekly budget checks Error Handling Error Cause Solut …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-policy-guardrails--31abb1