'sentry' 검색 결과

Inspect production errors recorded in Sentry through read-only API access. Summarize unresolved issues, recent crashes, occurrence counts, and event details to understand what happened and when each problem was last seen.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review unresolved production issues from the last 24 hours
• Summarize recent crashes and occurrence counts
• Inspect events linked to a specific issue

Investigate WorldMonitor production errors using Sentry event details and source code. Classify issues as noise, already fixed, product bugs, ingestion problems, or needing human review, with tested fixes when code changes are requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate an issue from a Sentry URL or short ID
• Review unresolved issues and muted error reports
• Test noise filters and fixes for product bugs

Review new and spiking Sentry errors, rank their impact, and check for existing GitHub issues. Create triage issues for the highest-impact untracked errors and post a Slack summary, while leaving Sentry error states and assignments unchanged.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review new and spiking errors every hour
• Avoid duplicate GitHub issues for Sentry errors
• Create issues with stack traces and impact details

Inspect production errors recorded in Sentry using read-only queries. The skill summarizes recent issues, retrieves details of individual error occurrences, and accesses AI-generated cause analysis or fix plans through the command-line tool.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing unresolved production issues from the last 24 hours
• Inspecting an issue by its short ID
• Checking individual error occurrences and release details

Investigate production errors using Sentry stack traces, which show the code execution path, and events leading up to the failure. Identify likely causes, triggering conditions, affected users, and releases before changing code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating an error from a Sentry link
• Finding what triggers user crashes
• Checking affected users and releases

Add Sentry error reporting and performance monitoring to services, scheduled jobs, and database operations. Follow examples for capturing exceptions with useful context and measuring execution time through spans, which record individual operations for investigation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding error reporting to an API
• Recording failures and execution time for scheduled jobs
• Measuring database and asynchronous operations

Investigate and fix production errors reported in Sentry through MCP, a connection to external tools. Analyze error details and execution history, check them against source code, implement fixes, and verify them with tests and regression checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating a specific Sentry issue
• Finding the root cause of production exceptions
• Working through unresolved errors with fixes and tests

Sentry の Issue 一覧 URL（例 `https://<org>.sentry.io/issues/?project=<id>&environment=<env>`）を受け取り、未解決（unresolved）の Issue を列挙して1件ずつサブエージェントで並列調査する。コード上で既に解消済みと確認できたものは Sentry 側を resolved にし、未解消のものは `create-issue` スキルで GitHub Issue を作成する。「Sentryのissueをトリアージして」「Sentryの未解決エラーをチケット化して」といった依頼で使用する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Investigate Sentry errors by fetching event details and the actions leading up to failures through Composio CLI. Connect error locations to local code, inspect suspect commits, propose patches, run tests, and rank unresolved issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate a new Sentry alert
• Trace a regression to suspect commits
• Rank unresolved errors by frequency

Investigate Sentry issues by comparing recent events, error locations in code, tags, environments, releases, and recurrence patterns. Separate observed failures from suspected causes before proposing a fix grounded in the available evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate a Sentry issue within a defined time window
• Compare errors across environments and releases
• Separate observed facts from suspected causes

Verify production fixes by connecting code changes and releases to Sentry issues. Compare error events and affected users before and after release, then report whether the fix worked, improved behavior, failed, or lacks enough traffic to judge.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether the release containing a fix appears in Sentry
• Compare error events and affected users before and after release
• Assess improvement, regression, or insufficient traffic

Investigate Sentry alerts using Datadog logs and recent GitHub changes, then post an initial diagnosis with a severity assessment. Notify the on-call team when severity reaches the configured threshold or the investigation remains inconclusive, without changing monitored systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate new and unresolved Sentry alerts
• Compare failures with logs and recent deployments
• Notify on-call staff for severe or inconclusive alerts

Investigate service errors in Sentry by project, environment, and time period. Rank problems by event counts and affected users, compare releases or earlier periods, and report findings with links and a clear search scope.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing errors affecting production
• Checking changes after a release
• Comparing service stability across periods

Investigate opaque errors in shipped OpenWork builds using local logs and Sentry exception reports. Identify the change that caused the failure, reproduce it on the affected runtime, file a Linear issue, and reply to the original report.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating unexplained errors in shipped OpenWork builds
• Identifying the PR that introduced a failure
• Reproducing errors on the affected runtime

Set up Sentry error tracking, investigate production failures, and prioritize issues by user impact. Configure useful alerts and analyze performance traces, which show how time is spent across application operations and services.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up application error tracking
• Investigating production errors
• Prioritizing issues by user impact

Integrates Sentry error tracking and performance monitoring into Flutter apps using `sentry_flutter`. Use when setting up crash reporting in Flutter, calling `SentryFlutter.init`, adding `SentryNavigatorObserver` to GoRouter, tracing HTTP requests with `sentry_dio`, capturing handled exceptions via `Sentry.captureException`, adding breadcrumbs, configuring session replay (`replay.onErrorSampleRate`), tuning `tracesSampleRate` or `profilesSampleRate`, controlling PII with `sendDefaultPii`, or setting user context after login and logout.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up recurring agent work for issues, tickets, or small fixes. The skill tests one real item first, then defines a repeatable procedure, tracks work to prevent duplicates, and holds outputs for human review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recurring preparation of fixes for Sentry issues
• Drafting replies to Front tickets
• Preparing small performance improvement PRs

Assesses a release using Sentry errors, recurring problems, affected users, and crash evidence. Compares equivalent periods with the previous stable release, identifies gaps in the evidence, and recommends rollout actions only when the findings support them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing a production release with the previous stable version
• Reviewing new or recurring issues and their user impact
• Checking whether quiet results reflect missing data

Compare Sentry issues across selected time windows and releases to find new or recurring problems and changes in frequency or affected users. Prioritize findings using user impact and the strength of available evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compare issues before and after a release
• Find recurring issues and frequency changes
• Prioritize issues by affected users

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Query and manage Sentry error-tracking data — list and search issues, drill into events and stack traces, inspect projects and releases, resolve/ignore issues, and pull stats. Use this whenever the user mentions a Sentry issue, crash, error group, or exception; pastes a sentry.io or self-hosted Sentry URL; asks "why is this erroring", "how many times has this happened", "what's the top error in {project}", "resolve this issue", or wants a Sentry-based digest — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.