sentry-javascript-bugs

Detect recurring frontend bug patterns in Sentry JavaScript projects during code reviews.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/Harigithub11/sentry --skill sentry-javascript-bugs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-javascript-bugs
Source: https://github.com/Harigithub11/sentry/tree/main/.agents/skills/sentry-javascript-bugs
Command: npx skills add https://github.com/Harigithub11/sentry --skill sentry-javascript-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Frontend bug patterns from production issues and code changes can escape quick triage, causing regressions and slower fixes.

Core Features & Use Cases

  • Detects common frontend bug patterns drawn from production issues and PR reviews.
  • Provides pattern-based checks and references to guide code reviews and debugging sessions.
  • Use case: during a PR review, surface high-confidence bug patterns that commonly cause production errors.

Quick Start

Run the skill against the current branch diff to surface high-priority bug patterns and guide fixes.

Frequently Asked Questions about sentry-javascript-bugs

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

FAQPage Schema
How do I find recurring JavaScript frontend bug patterns during a code review?

JavaScript frontend bug patterns are recurring code issues like null/reference errors and improper API response handling that cause production crashes. Identifying them during code reviews or branch diffs prevents regressions by surfacing high-confidence failure patterns before deployment.

How do I surface Sentry production issues faster from my current branch?

To surface Sentry production issues faster, run pattern-based checks against your current branch diff to identify trace view integrity failures and reference errors. This matches new code changes against documented frontend failure patterns to guide immediate debugging and fixes.

Can I use this to review Warden findings for frontend JavaScript errors?

Yes, you can apply this to Warden findings to review frontend JavaScript errors. It enforces structured checks against null/reference errors, API response handling, and trace view integrity, matching Warden's reported issues against documented production bug patterns to validate and guide fixes.

What types of frontend failure patterns does this check for in JavaScript code?

It checks for frontend failure patterns including null/reference errors, API response handling issues, and trace view integrity failures in JavaScript code. These structured checks are drawn from documented production issues and PR reviews to surface high-confidence bug patterns.

Does this work for analyzing frontend diffs without additional dependencies?

Yes, it works for analyzing frontend diffs without additional dependencies. The Skill operates independently using internal references to guide code reviews and debugging sessions, requiring no external packages to surface high-priority bug patterns from your current branch or PR changes.