sentry-response

Automates end-to-end handling of Sentry issues including investigation, fixes, PRs, and closure.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/VibeTechnologies/VibeTeam --skill sentry-response
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-response
Source: https://github.com/VibeTechnologies/VibeTeam/tree/main/agents/SoftwareEngineer/skills/sentry-response
Command: npx skills add https://github.com/VibeTechnologies/VibeTeam --skill sentry-response

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sentry-response handles Sentry issues end-to-end for SoftwareEngineer (investigate, fix, PR, and close).

Core Features & Use Cases

  • Detect and manage Sentry issues via MCP tools or sentry-cli to retrieve details and stack traces.
  • Create, reference, and link pull requests to Sentry issues, and close issues after merge.
  • Applicable when a task references a Sentry URL/ID, a Support Engineer escalates a bug for code fixes, or a request asks to check Sentry and deliver a code change.

Quick Start

Use the sentry-response skill to respond to a Sentry issue by fetching its details and proposing a fix plan.

Frequently Asked Questions about sentry-response

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

FAQPage Schema
How do I automate Sentry issue resolution and create a pull request for the fix?

Sentry issue resolution can be automated by using the sentry-response Skill to fetch issue details and stack traces, propose a fix plan, and create a linked pull request on GitHub to close the ticket.

What is the end-to-end process for managing escalated Sentry bugs?

End-to-end Sentry bug management involves retrieving issue data via MCP tools or sentry-cli, generating a code fix, creating a pull request, linking it to the Sentry issue, and resolving the ticket after the PR merges.

Do I need a Sentry auth token and GitHub access to automate issue management?

Yes, automating Sentry issue management requires a SENTRY_AUTH_TOKEN and GitHub access to fetch issue data, create pull requests, link issues, and resolve tickets through MCP tools or sentry-cli.

Can I use sentry-cli instead of MCP tools to investigate and fix Sentry issues?

Yes, you can use sentry-cli as an alternative to MCP tools to detect Sentry issues, retrieve details and stack traces, and manage the end-to-end resolution workflow including pull request creation.

When should I use an automated workflow for Sentry issue tracking?

You should use an automated workflow for Sentry issue tracking when a task references a Sentry URL or ID, or when a Support Engineer escalates a bug requiring code fixes and a deliverable pull request.

How do I link a pull request to a Sentry issue after merging a fix?

To link a pull request to a Sentry issue, the automation workflow references the Sentry issue within the PR and automatically closes or resolves the Sentry ticket after the pull request is successfully merged.