Skill UI

This comprehensive guide details how to harden Sentry's security posture and ensure compliance with regulations like GDPR. It covers best practices for managing sensitive data, implementing PII scrubbing, and configuring `beforeSend` hooks to automatically redact sensitive information such as passwords, API keys, tokens, IP addresses, and emails from client-side and server-side events.

This skill guides developers through major Sentry SDK version upgrades (e.g., v7 to v8, Python v1 to v2). It helps detect deprecated APIs, runs automated codemods (like @sentry/migr8), and applies manual fixes for breaking changes, ensuring a smooth transition while maintaining robust error tracking and observability.

This guide provides a comprehensive setup for Vercel observability. It covers enabling built-in analytics, collecting detailed runtime logs, implementing structured logging, configuring external log drains (e.g., Datadog, Sentry), and integrating OpenTelemetry tracing. Use this when monitoring production deployments and setting up robust error tracking.

This skill enforces Sentry's rigorous blog writing standards, ensuring all content—from deep technical dives to product announcements—reads like it was written by a senior developer. It guides users on adopting a specific, opinionated, and technically credible voice, structuring posts around problem-solving, and avoiding generic corporate jargon.

This skill helps users create a new Git branch that strictly adheres to established project naming conventions (e.g., Sentry standards). It automatically determines the appropriate branch type (such as `feat`, `fix`, `chore`, etc.) and generates a descriptive, standardized branch name by analyzing the provided work description or local code differences (diff). It guides the entire branching workflow, ensuring proper lineage and classification for code submissions.

samber/oops is a robust library that transforms standard Go error handling by adding crucial structured context. Instead of generic error messages, it allows developers to attach key-value attributes, stack traces, error codes, and user-facing messages directly to the error object. This is essential for modern microservices, allowing APM tools (Datadog, Sentry) and on-call engineers to diagnose failures accurately by understanding the full context of the failure, such as the domain, user ID, and specific query that failed.

A comprehensive toolkit for building robust, structured logging pipelines in Golang. It provides advanced modules for handler composition (slog-multi), throughput control (slog-sampling), attribute transformation (slog-formatter), and integrates with major backend logging sinks (e.g., Sentry, Loki, Datadog, Elasticsearch). Use this when building complex Go applications that require deterministic log routing, sampling, and data sanitization.

A comprehensive automation toolkit for managing Sentry error tracking and monitoring operations. Users can programmatically investigate issues, configure project-level alert rules, manage release versions, and monitor organizational structure. Essential for DevOps and development teams needing deep integration and programmatic control over error data.

This CLI tool automates the entire issue triage lifecycle for Linear and Jira. Users can pull backlogs, cluster duplicates, apply labels, reassign owners, and post detailed summaries—all directly from the shell. It is ideal for weekly backlog cleanup, post-release bug sweeps, and synchronizing data between multiple tools (e.g., Sentry to Linear).

This tool automates the diagnosis of production errors tracked by Sentry. By leveraging the Composio CLI, it retrieves comprehensive issue details, full stack traces, breadcrumbs, and associated commits. It maps stack frames to local source code, allowing agents to propose fixes and triage issues directly, eliminating manual copy-pasting.