skills.rest
prof18
prof18COMMUNITY
Explore all skills by this author →
Website𝕏@marcoGomierGitHub

sentry-note-crash-fix

Investigate and fix FeedFlow crashes from Sentry triage notes and issue URLs.

1.2k|63|Updated Feb 11, 2023
Search Tags:#stack trace#gradle#issue triage#Sentry#Debugging#kotlin multiplatform#crash fix
One-click install
npx skills add https://github.com/prof18/feed-flow --skill sentry-note-crash-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sentry-note-crash-fix
Source: https://github.com/prof18/feed-flow/tree/main/.ai/skills/sentry-note-crash-fix
Command: npx skills add https://github.com/prof18/feed-flow --skill sentry-note-crash-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crash reports arrive as scattered notes, Gmail exports, or Sentry links, and turning them into verified root-cause fixes requires manual triage, repository searching, and validation. This Skill walks an AI agent through the full loop: reading the note, fetching live Sentry context, diagnosing the crash, deciding whether it is worth fixing, implementing the fix, validating it, and optionally committing and resolving the Sentry issue.

Core Features & Use Cases

  • Sentry context retrieval: Extracts issue IDs, event IDs, releases, and stack frames from notes or URLs, then fetches live issue and event data through Sentry MCP tools or CLI helpers.
  • Root-cause diagnosis and impact triage: Identifies the first-party frame versus the throwing library frame, weighs occurrence counts and affected users, and explicitly supports skipping low-impact or noise reports without speculative fixes.
  • Guided fix and validation: Searches the repo with rg, checks dependency versions in gradle/libs.versions.toml, applies narrow patches, and runs targeted Gradle builds, detekt, and tests before handoff.
  • Use Case: A user pastes a Sentry issue URL for a crash in the FeedFlow desktop app and asks for a fix; the Skill fetches the event, traces the crash to a dependency API change, patches the call site, runs :desktopApp:compileKotlinJvm, and resolves the Sentry issue with the commit reference.

Quick Start

Use $sentry-note-crash-fix to investigate and fix the crash described in this Sentry issue URL.

Frequently Asked Questions about sentry-note-crash-fix

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

FAQPage Schema
How do I fix a crash reported in Sentry?▼

Provide the Sentry issue URL, event ID, or a triage note and ask for an investigation. The Skill fetches live issue context, identifies the first-party frame and throwing library, implements a narrow root-cause fix, and validates it with targeted Gradle builds and tests.

How to triage whether a Sentry crash is worth fixing?▼

The Skill weighs live Sentry data such as affected users, occurrence count, recurrence, releases, and platforms. It skips issues that are exotic, affect very few users, or are expected-environment noise, and explains the skip reason instead of inventing a fix.

What inputs does the Sentry crash investigation accept?▼

It accepts local note file paths, note URLs, Gmail-exported notes, Sentry issue URLs, issue IDs, and event IDs. It extracts release, platform, exception type, and stack frames from the note, then confirms details against live Sentry data.

Does it work without Sentry MCP tools configured?▼

Yes, it falls back to an installed Sentry skill or CLI helper when MCP tools are unavailable. If CLI authentication is missing, it asks you to set the SENTRY_AUTH_TOKEN environment variable rather than pasting a token into chat.

Will it commit the fix and resolve the Sentry issue automatically?▼

Only when explicitly asked. It stages only fix-related files with a one-line commit message, keeps Sentry ticket references out of the message unless requested, and resolves the issue via update_issue with the commit hash and fix summary.

Why does the investigation stop without code changes?▼

It stops when the report is telemetry noise, expected user or environment failure, or an edge case with no clear product impact. It states the concrete skip reason and any uncertainty, such as missing Sentry auth or stale occurrence counts.

Related Skills

Explore More Software Engineering Skills→
WhaleylawWhaleylaw

error-tracking-specialist

Analyze stack traces and error context to triage production application errors.

Community
Intermediate
Devin-AXISDevin-AXIS
5.3k

sentry-fix-verification

Verify production fixes by comparing Sentry issue events before and after a release.

Community
Basic
z1439527767z1439527767

phase-gated-debugging

Guide software debugging through five phases with root cause confirmation before fixes.

Community
Advanced
IntelliTectIntelliTect

add-accessibility

Audit and remediate accessibility gaps in Vuetify components for WCAG compliance.

Official
Advanced