Skill UI

This skill provides a rigorous framework for tackling complex software development tasks. It guides users to break down large features, refactoring efforts, or bug fixes into small, actionable, and independently verifiable steps. By focusing on clear outcomes, dependencies, and specific verification criteria, it ensures that the implementation process is structured, manageable, and traceable from start to finish.

Set up comprehensive CI/CD pipelines for PostHog integrations using GitHub Actions. This guide covers mocked unit tests (no API key needed), robust integration tests against a development PostHog project, and automated deployment annotations to mark releases in your PostHog timeline. Ideal for developers ensuring data quality and traceability across all environments.

This comprehensive workflow guides developers through implementing full-stack product analytics using PostHog. It covers key areas including defining event taxonomies, capturing user actions (client-side), identifying and updating user properties, and performing B2B group analytics. It also demonstrates server-side event tracking using posthog-node, ensuring a complete, accurate, and traceable view of user behavior and product usage across web, mobile, and API sources.

A comprehensive guide to integrating Sentry into continuous integration and continuous deployment (CI/CD) pipelines (e.g., GitHub Actions, GitLab CI, CircleCI). This skill automates complex tasks such as creating releases, uploading source maps for readable stack traces, associating commits, and tracking deployment environments, ensuring rapid and accurate debugging of production errors.

A structured framework for managing production outages using Sentry. This guide walks users through classifying incident severity (P0-P3), performing deep triage using stack traces and breadcrumbs, and executing API-based queries to pinpoint root causes and measure impact. Essential for DevOps and SRE teams during critical incident response.

This skill guides the setup of distributed tracing and performance monitoring using Sentry. It covers configuring the SDK (e.g., setting tracesSampleRate) to capture latency, identify performance bottlenecks, and trace requests across the entire application stack. It demonstrates how to create manual spans for business logic and utilizes profiling for deeper performance insights, ensuring comprehensive application observability.

A comprehensive guide to optimizing Sentry's performance monitoring pipeline. Learn how to minimize SDK overhead and event costs while maximizing signal quality. Techniques covered include replacing static sampling rates with dynamic `tracesSampler`, configuring profiling rates, preventing cardinality explosion through proper transaction naming, and implementing custom measurements for deeper business logic visibility. Essential for high-traffic, production applications.

This framework enforces organizational governance and policy guardrails for Sentry usage. It standardizes configuration across services, mandatorily scrubbing PII, enforcing naming conventions, and managing trace rate caps based on service criticality. It integrates into CI/CD to prevent compliance drift and ensure adherence to standards like GDPR and HIPAA.

A comprehensive checklist for ensuring Sentry is properly configured before any production deployment. This guide covers best practices for managing environment variables (DSN), implementing release tracking, optimizing error and trace sample rates, uploading source maps, and filtering noise. Essential for go-live readiness and auditing existing monitoring setups.

A comprehensive guide to managing Sentry's event volume, quotas, and rate limits. Learn how to prevent 429 Too Many Requests errors and control costs by implementing client-side sampling (sampleRate/tracesSampleRate), using beforeSend filters to drop noisy errors, and understanding various quota types (Errors, Transactions, Replays). Essential for high-volume, cost-sensitive applications.

This guide details how to use the Sentry CLI to manage the full application release lifecycle. Users can create versioned releases (using Semver or SHA), upload source maps to deminify stack traces, and associate specific git commits. This ensures that every error is accurately linked to the exact code version and deployment that caused it, significantly improving debugging and observability in CI/CD pipelines.

A comprehensive guide covering observability patterns for service meshes like Istio and Linkerd. Learn how to implement the three pillars—Metrics, Traces, and Logs—to monitor service health, visualize dependencies, track golden signals (latency, traffic, errors, saturation), and debug microservice communication issues across complex distributed systems.