sentry
Sentry error monitoring integration. Access error reports, analyze stack traces, search issues by fingerprint, and debug production errors directly from your development environment.
Summary
The Sentry skill integrates Sentry error monitoring directly into your development environment, allowing you to access error reports, analyze stack traces, search issues by fingerprint, and debug production errors without leaving your code editor.
- It streamlines the debugging workflow by providing instant visibility into application errors and performance issues.
Install & Usage
/plugin marketplace add <org/repo>Add the configuration to /plugin install sentry@<marketplace>
/pluginUse Cases
Usage Examples
/sentry list recent errors for project 'my-app'
/sentry analyze stack trace from issue SENTRY-123
/sentry search issues by fingerprint 'deadlock-abc'
Security Audits
Frequently Asked Questions
What is sentry?
The Sentry skill integrates Sentry error monitoring directly into your development environment, allowing you to access error reports, analyze stack traces, search issues by fingerprint, and debug production errors without leaving your code editor. It streamlines the debugging workflow by providing instant visibility into application errors and performance issues.
How to install sentry?
To install sentry: add a marketplace (/plugin marketplace add <org/repo>), then add the config to /plugin install sentry@<marketplace>. Finally, /plugin in Claude Code.
What is sentry best for?
sentry is a plugin categorized under General. Created by Anthropic.
What can I use sentry for?
sentry is useful for: Quickly view the latest error reports for a specific project to identify new issues.; Analyze a stack trace from a production error to pinpoint the root cause in your code.; Search for issues by fingerprint to find all occurrences of a specific bug across environments.; Retrieve detailed event data for a specific error ID to understand the context of a failure.; List unresolved issues assigned to a team member to prioritize debugging efforts.; Compare error frequency trends over time to detect regressions after a deployment..