Agent skill · marketing growth · thebushidocollective
sentry-alerts-issues
Use when configuring Sentry alerts, managing issues, or setting up notifications. Covers alert rules, issue triage, and integrations.
Why this skill is useful
Provides specific API commands and integration patterns for managing Sentry alerts and issues that the AI wouldn't reliably generate on its own.
What it needs
Requires sentry account access. About 2k tokens when loaded. Last updated 2026-07-19. 187 stars on the source repository.
What this skill does
Sentry - Alerts & Issue Management Configure alerts, manage issues, and set up notifications. Alert Types Issue Alerts Trigger when an issue matches specific conditions: New issue created Issue changes state (resolved → unresolved) Issue frequency exceeds threshold Issue affects specific users/releases Metric Alerts Trigger based on aggregate metrics: Error count exceeds threshold Transaction latency (p50, p95, p99) Failure rate percentage Apdex score drops Uptime Monitoring Monitor endpoint availability: HTTP status codes Response time thresholds SSL certificate expiration Alert Conditions Frequency-Based User Impact First Seen Regression Alert Actions Notification Channels Email: Individual or team distribution Slack: Channel or direct messages PagerDuty: On-call escalation Discord: Webhook notifications Microsoft Teams: Channel posts Webhooks: Custom integrations Issue Actions Assign to team member Add tags Create ticket (Jira, Linear, GitHub) Issue States Lifecycle 1. Unresolved: Active issue needing attention 2. Resolved: Fixed in a release 3. Ignored: Intentionally dismissed 4. Archived: Historical, no longer tracked Substates For Review: Needs triage Escalating: Increasing in frequency Regressed: Previously resolved, now recurring New: First seen recently Issue Management Merge Issues Combine duplicate issues with different stack traces: 1. Select issues to merge 2. Choose primary issue 3. All events appear under primary Ignore Rules Ownership Rules API Integration List Issues Update Issue Create Alert Rule Integration Examples Slack Alert PagerDuty Escalation Jira Ticket Creation Best Practices 1. Start with conservative thresholds, tune over time 2. Use different channels for different severities 3. Set up on-call rotation for critical alerts 4. Review and archive stale issues regularly 5. Define ownership rules for automatic assignment 6. Create runbooks for common alert types 7. Use metric alerts for SLO monitoring
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thebushidocollective/alerts-issues