133건 · 관련도순
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`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organize Linear or Jira backlogs through the Composio CLI, a command-line tool. Fetch issues in bulk, group likely duplicates, update labels, priorities, and owners, then share a summary of changes in Slack.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build Node.js, Express, and TypeScript APIs with consistent structure. Separate request handling, business logic, and database access, while following guidance for input validation, error tracking, configuration, and tests when adding features or refactoring existing services.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Triage Sentry errors: list organizations, projects, and recent issues; resolve, archive, and assign issues. Trigger phrases: sentry, sentry errors, error tracking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add Temps error tracking to applications using the Sentry-compatible SDK. Temps exposes a Sentry-compatible DSN that works with the official Sentry SDK for each language/framework — no code changes beyond initialization are required. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue, Svelte, Angular, Node.js, Python, Go, Rust, Ruby, Java, PHP, .NET, React Native, Flutter), (2) Wire up uncaught exception and unhandled promise rejection capture, (3) Configure session replay for errors, (4) Upload source maps for readable stack traces, (5) Report releases and environments, (6) Capture custom errors/messages. Triggers: "add error tracking", "add sentry", "track exceptions", "report errors", "temps error tracking", "wire up error monitoring".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user shares a Sentry URL, says "check Sentry", or wants to investigate production errors. Uses Sentry MCP tools for deep analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up or review production error monitoring to capture unhandled errors, failed requests, and performance signals. Check event context, release labels, and alert routing so teams receive useful information when problems occur.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize Node.js, Express, and TypeScript APIs into layers with clear responsibilities. This guide covers request handling, business logic, database access, input validation, error tracking, configuration, and testing to support consistent implementation and refactoring across services.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate a possible incident in Superset’s hosted services by checking deployments, error spikes, and service health. Produce a proposed severity and status page update for human review, without changing services or publishing messages.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the official Sentry CLI to investigate issues, events, traces, and logs for Vibe Remote without committing Sentry credentials into the repository.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design resilient React error handling with Error Boundaries, Sentry integration, recovery UI, retry patterns, and graceful degradation. Activate on: error boundary, crash recovery, Sentry, error fallback UI, retry logic, unhandled exceptions. NOT for: form validation errors (use form-validation-architect), API error codes (use api-architect).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design resilient React error handling with Error Boundaries, Sentry integration, recovery UI, retry patterns, and graceful degradation. Activate on: error boundary, crash recovery, Sentry, error fallback UI, retry logic, unhandled exceptions. NOT for: form validation errors (use form-validation-architect), API error codes (use api-architect).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze and fix production errors from Sentry crash reports. Use when investigating AppHang, ANR, crashes, or production errors. Includes complete workflow from JSON analysis to bug fix implementation with evidence-based methodology. Triggers on sentry, crash, AppHang, ANR, error analysis, production error, bug analysis, crash report, freeze, hang, not responding, stacktrace, breadcrumbs, exception.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sentry error tracking and monitoring for OneKey. Use when configuring Sentry, filtering errors, analyzing crash reports, or debugging production issues. Covers platform-specific setup (desktop/mobile/web/extension) and error filtering strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find and call tools in connected services such as Linear and GitHub through superset mcp. This skill also helps diagnose connection and permission errors and access tools missing from an agent’s own tool list.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture screenshots of the Sentry UI in a web browser, lay them out in a pull request description as before/after tables, and upload them with `gh --attach`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Document and type a Sentry API endpoint. Write or fix @extend_schema decorators, specify response TypedDicts, type request parameters, correct type drift between the declared schema and the runtime response, and validate the generated spec. Use when asked to "document an endpoint", "add OpenAPI docs", "add/fix @extend_schema", "type an endpoint response", "fix the response type", "fix type drift", "reuse a response type", "split an overloaded endpoint", "specify the response schema", "add a TypedDict response", "migrate a legacy api-docs path", "fix a parameter type", or "make an endpoint public" / "promote an endpoint" (promotion is one section here).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.