133건 · 관련도순
Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add Sentry v8 error tracking and performance monitoring to your project services. Use this skill when adding error handling, creating new controllers, instrumenting cron jobs, or tracking database performance. ALL ERRORS MUST BE CAPTURED TO SENTRY - no exceptions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions, error tracking with Sentry, payload encryption for sensitive data, dependency injection of clients (DB, Stripe, etc.) into function handlers, custom telemetry, or behavior that should apply uniformly across many functions. Covers Inngest middleware lifecycle, creating custom middleware, dependencyInjectionMiddleware, @inngest/middleware-encryption, @inngest/middleware-sentry, and custom middleware patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze application error logs and monitoring platform exports (Sentry, Datadog, Rollbar) to identify error patterns, duplicates, and severity. Use when someone asks to "audit errors", "analyze exceptions", "find noisy alerts", "deduplicate error groups", or "triage production errors". Parses JSON/CSV error exports and produces categorized reports with root cause analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert at making systems observable and debuggable. Covers structured logging, metrics collection, distributed tracing, error tracking, and alerting. Knows how to find the needle in the haystack when production breaks at 3 AM. Use when "observability, logging, metrics, tracing, monitoring, error tracking, Sentry, Datadog, OpenTelemetry, debugging production, observability, logging, metrics, tracing, monitoring, sentry, prometheus, opentelemetry" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod env + probes), and consumed by l3-support (traces) and devops (deploy gate).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guide for structured logging (Pino, Winston), error tracking (Sentry), log aggregation (Axiom, Datadog), request correlation, and GDPR-compliant log management / Panduan ahli untuk logging terstruktur (Pino, Winston), pelacakan error (Sentry), agregasi log, korelasi request, dan manajemen log sesuai GDPR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sentry error tracking and performance monitoring for real-time visibility into application errors, performance issues, and release health
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions, error tracking with Sentry, payload encryption for sensitive data, dependency injection of clients (DB, Stripe, etc.) into function handlers, custom telemetry, or behavior that should apply uniformly across many functions. Covers Inngest middleware lifecycle, creating custom middleware, dependencyInjectionMiddleware, @inngest/middleware-encryption, @inngest/middleware-sentry, and custom middleware patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pino logging, Sentry error tracking, Axiom - structured logging with correlation IDs, error boundaries, performance monitoring, alerting
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pino, Axiom, Sentry installation - one-time project setup for logging and error tracking with source maps upload
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full instrumentation from day one. PostHog consolidates product analytics + feature flags + error tracking (one platform, one bill). GA4 via GTM (14-step automation, custom dimensions over events, server-side tagging). Sentry (deep error tracking + performance). Stripe (webhook-first with idempotent processing). Listmonk on Coolify (newsletters via Amazon SES SMTP relay). PLG 7-layer framework. Programmatic SEO (5 page types). Incident auto-remediation via Sentry→Inngest pipeline. AI search (GEO) awareness. Local business conversions (phone_click, direction_click, form_submit, booking_click) with CRO patterns for both SaaS and local.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sentry Unity SDK integration patterns for error tracking, performance monitoring, transactions, spans, and custom instrumentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose Sentry issues without copy-pasting stack traces. Uses the Composio CLI to pull issue details, events, breadcrumbs, and suspect commits, then maps the frames to local source so the agent can propose a fix directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query Sentry issues, events, releases, replays, and org/project metadata via REST API. Use when the user wants to diagnose a production error, pull stack traces, list recent issues, inspect a release, or fetch event data programmatically — prefer this over asking for UI screenshots or guessing from memory.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sentryのイシューを調査して修正する。リンク・ID・検索でイシューを 特定し、スタックトレース・ブレッドクラム・トレース・ログの全コンテキストを 取得し、根本原因を特定して修正・解決する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze Sentry session replays to surface UX patterns, pain points, and user journeys for a given product area. Use when asked to "show me how users use", "day in the life", "UX research", "replay research", "how do customers use", "what's the user experience like for", "watch replays of", "analyze replays for", "user behavior on", or "replay UX audit" for any Sentry product surface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create data-driven presentation slides using React, Vite, and Recharts with Sentry branding. Use when asked to "create a presentation", "build slides", "make a deck", "create a data presentation", "build a Sentry presentation". Scaffolds a complete slide-based app with charts, animations, and single-file HTML output.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.