From sentry
Fetch a specific Sentry issue by ID and propose a targeted code fix. Use when the developer provides an issue ID, or after triage when they select an issue. Also use when they say "fix this sentry error", "debug issue ISSUE-123", "what caused this crash".
npx claudepluginhub dhruvtilva/sentryThis skill uses the workspace's default tool permissions.
Step 1: Use sentry_get_issue with issue_id = "$ARGUMENTS" to fetch full issue details
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Step 1: Use sentry_get_issue with issue_id = "$ARGUMENTS" to fetch full issue details including the latest stack trace.
Step 2: Read the stack trace carefully. Identify the exact file and line number of the error.
Step 3: Use the Read tool to read the actual source file from the local codebase.
Step 4: Analyze the root cause combining the stack trace + actual code.
Step 5: Propose a specific, minimal code fix. Show before/after diff format.
Step 6: Ask the developer if they want you to apply the fix directly.
If $ARGUMENTS is empty, ask the developer for the issue ID first.