sentry

Investigate Sentry errors and events via CLI with root-cause explanations.

Updated Jul 6, 2020
One-click install
npx skills add https://github.com/guifry/devconfig --skill sentry-guifry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry
Source: https://github.com/guifry/devconfig/tree/main/claude/skills/sentry
Command: npx skills add https://github.com/guifry/devconfig --skill sentry-guifry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sentry CLI enables fast investigation of errors, events, and logs across applications by providing command-line access to Sentry's features.

Core Features & Use Cases

  • Developer CLI: issue workflows, view & explain issues
  • Build CLI: release management, source maps, deployments
  • Authentication and settings management for both CLIs
  • Real-time insights and AI root-cause explanations for faster remediation

Quick Start

Authenticate with the Developer CLI using sentry auth login and start listing unresolved issues with sentry issue list.

Frequently Asked Questions about sentry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate Sentry errors and events from the command line?

You investigate Sentry errors and events by using Sentry CLI commands to list and view issues across development, staging, and production environments. This allows for fast issue lookup directly from your terminal.

Can I get AI root-cause explanations for Sentry issues via the CLI?

Yes, the Sentry Developer CLI provides AI root-cause explanations for issues, enabling faster remediation. You can view and explain unresolved errors directly through command-line workflows.

How do I authenticate before listing unresolved Sentry issues?

You authenticate by running sentry auth login to configure your credentials for the Developer CLI. Once authenticated, you can immediately list unresolved issues using sentry issue list.

Does Sentry CLI support release management and source maps?

Yes, the Build CLI workflow supports release management, source maps, and deployments. This allows you to manage application releases and trace errors back to specific deployments.

What is the best way to trace errors across staging and production environments?

The best way to trace errors across staging and production is using Sentry CLI for issue lookup and release tracing. It provides real-time insights and event logs to quickly identify root causes across environments.

Why should I use Sentry CLI instead of the web dashboard for debugging?

Using Sentry CLI for debugging provides command-line access to issue workflows, event logs, and AI root-cause explanations without leaving your terminal. This enables faster investigation and remediation across environments.