New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Sentry Javascript Bugs

by getsentry in getsentry/sentry

Review Sentry React and TypeScript changes for bug patterns drawn from real production issues.

OfficialCustom licenceAuto-check: notesFrontend & Design

Install Sentry Javascript Bugs

skills CLI
$ npx skills add getsentry/sentry --skill sentry-javascript-bugs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install getsentry/sentry sentry-javascript-bugs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sentry-javascript-bugs .claude/skills/sentry-javascript-bugs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sentry-javascript-bugs
GitHub stars
45k
Token cost
~2.6k tokens
SKILL.md length
1,243 words
Files
9 (incl. references)
Skills in repo
29
Repo updated
First seen
Licence
Custom licence

At a glance

Review Sentry React and TypeScript changes for bug patterns drawn from real production issues.

  • Works in 3 steps: Classify the Code → Check for Top Bug Patterns → Report Findings
  • Reviewing a frontend diff
  • SKILL.md covers Scope, Step 1: Classify the Code, Step 2: Check for Top Bug… and Step 3: Report Findings
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sentry Javascript Bugs is an agent skill from getsentry/sentry, published by the product's own GitHub organization. Review Sentry React and TypeScript changes for bug patterns drawn from real production issues. Use when reviewing a frontend diff or PR, checking Warden findings, auditing the current branch, reviewing production-error patterns, or looking for common regressions in static/.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `README.md`, `references/ai-insights-parsing.md` and `references/api-response-handling.md`).

It sits in Frontend & Design. It works with Sentry, JavaScript, React and TypeScript. The repository describes itself as: Developer-first error tracking and performance monitoring.

When your agent uses it

  • Reviewing a frontend diff
  • Checking Warden findings
  • Auditing the current branch
  • Reviewing production-error patterns

Example prompts

  • “/sentry-javascript-bugs”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Classify the Code
  2. Check for Top Bug Patterns
  3. Report Findings

What it can do on your machine

Read from SKILL.md and the folder at commit 87d1203. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sentry Javascript Bugs loads about 2.6k tokens when it runs, and up to ~8.7k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 1,243 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,243 words (~2,610 tokens).

“Find bugs in Sentry frontend code by checking for the patterns that cause the most real production errors.”

— opening of SKILL.md by getsentry, Custom licence
name
sentry-javascript-bugs
allowed-tools
Read, Grep, Glob, Bash

Read the full SKILL.md on GitHub

Files

SKILL.md and 8 other files (references) in .agents/skills/sentry-javascript-bugs of getsentry/sentry.

  • SKILL.md
  • README.md
  • references/ai-insights-parsing.md
  • references/api-response-handling.md
  • references/dashboard-widget-errors.md
  • references/null-reference-errors.md
  • references/range-and-bounds-errors.md
  • references/react-lifecycle-errors.md
  • references/trace-view-errors.md

Open the folder on GitHubat commit 87d1203

Compare with similar skills

Sentry Javascript Bugs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sentry Javascript Bugs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sentry Javascript Bugs this skillgetsentry/sentry45k—~2.6kAutomated safety check: NotesCustom licence
Typescript Best Practicesbretzel-app/crumbs1271 repos~2.2kAutomated safety check: PassMIT
Connect Component To Figmadequelabs/cauldron129—~2kAutomated safety check: PassMPL-2.0
Frontend UIoomol-lab/open-flow223—~857Automated safety check: PassApache-2.0
Fork And GoSimplePDF/simplepdf-embed407—~7.9kAutomated safety check: NotesMIT
Javascript Practiceseser/stack128—~599Automated safety check: PassCustom licence

Similar skills

  • Typescript Best Practices

    bretzel-app/crumbs

    Provides TypeScript patterns for type-first development, making illegal states unrepresentable, exhaustive handling, and runtime validation.

    127 GitHub starsUsed in 1 repo~2.2k tokens
    Frontend & DesignAuto-check passed

  • Connect Component To Figma

    dequelabs/cauldron

    Add a Figma Code Connect (.figma.tsx) file for a Cauldron React component.

    129 GitHub stars~2k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Frontend UI

    oomol-lab/open-flow

    Implement and review Open Flow frontend components, styling, layout, and interactions.

    223 GitHub stars~857 tokensUpdated today
    Frontend & DesignAuto-check passed

  • Fork And Go

    SimplePDF/simplepdf-embed

    Guided walkthrough for forking and deploying your own SimplePDF Copilot: hosting choice, Pro-account confirmation, AI-provider wiring, demo customization, deploy, and the SimplePDF whitelist step.

    407 GitHub stars~7.9k tokensUpdated 7 days ago
    Frontend & DesignAuto-check: notes

  • Javascript Practices

    eser/stack

    TS and JS conventions for eserstack packages: namespace imports, mod.ts entries, cross-runtime APIs, explicit checks, async, tests and laroux React components.

    128 GitHub stars~599 tokensUpdated 3 days ago
    Frontend & DesignAuto-check passed

  • Migrate Webapi Selectall

    microsoft/power-platform-skills

    Official

    Reviews and migrates deprecated wildcard () values in Power Pages Web API fields site settings to least-privilege explicit Dataverse columns.

    967 GitHub stars~5.3k tokensUpdated today
    Frontend & DesignAuto-check: notes

More from getsentry/sentry

All 29 skills in this repo

  • Scraps Review

    getsentry/sentry

    Official

    Filter large Sentry Scraps design-system migration PRs for review by separating mechanical import-path changes, generated baseline updates, snapshot mocks, and pure renames from substantive…

    45k GitHub stars~1.2k tokensUpdated today
    Auto-check: notes

  • Analytics

    getsentry/sentry

    Official

    Instrument and discover analytics events in Sentry's frontend UI.

    45k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Hybrid Cloud Outboxes

    getsentry/sentry

    Official

    Guide for creating and maintaining outbox-based eventually consistent operations in Sentry.

    45k GitHub stars~4.8k tokensUpdated today
    Auto-check passed

  • Hybrid Cloud Rpc

    getsentry/sentry

    Official

    Guide for creating, updating, and deprecating hybrid cloud RPC services in Sentry.

    45k GitHub stars~4k tokensUpdated today
    Auto-check passed

  • Hybrid Cloud Test Gen

    getsentry/sentry

    Official

    Generate hybrid cloud tests for the Sentry codebase. An agent skill from getsentry/sentry.

    45k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Lint Fix

    getsentry/sentry

    Official

    Fix violations of an eslintPluginScraps rule across the codebase.

    45k GitHub stars~1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Sentry Javascript Bugs

What does Sentry Javascript Bugs do?

Review Sentry React and TypeScript changes for bug patterns drawn from real production issues. Sentry Javascript Bugs is an agent skill from getsentry/sentry, published by the product's own GitHub organization. Review Sentry React and TypeScript changes for bug patterns drawn from real production issues.

When should I use Sentry Javascript Bugs?

Sentry Javascript Bugs fits situations like: reviewing a frontend diff; checking Warden findings; auditing the current branch; reviewing production-error patterns.

How do I install Sentry Javascript Bugs in Claude Code?

Run `npx skills add getsentry/sentry --skill sentry-javascript-bugs -a claude-code`. Or copy the skill folder (.agents/skills/sentry-javascript-bugs in getsentry/sentry) into .claude/skills/sentry-javascript-bugs in your project. Claude Code loads it when a task matches its description.

How do I install Sentry Javascript Bugs in Codex?

Run `npx skills add getsentry/sentry --skill sentry-javascript-bugs -a codex`. Or copy the skill folder (.agents/skills/sentry-javascript-bugs in getsentry/sentry) into .agents/skills/sentry-javascript-bugs in your project. Codex loads it when a task matches its description.

Can I use Sentry Javascript Bugs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/sentry --skill sentry-javascript-bugs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry-javascript-bugs, .gemini/skills/sentry-javascript-bugs, .github/skills/sentry-javascript-bugs and .opencode/skills/sentry-javascript-bugs in your project.

What does Sentry Javascript Bugs need to run?

SKILL.md names no scripts, command-line tools or credentials: Sentry Javascript Bugs is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash.

Does Sentry Javascript Bugs access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sentry Javascript Bugs safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Sentry Javascript Bugs use?

Sentry Javascript Bugs has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Sentry Javascript Bugs use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.1k tokens, read only when the agent opens those files.

What are the alternatives to Sentry Javascript Bugs?

Skills that share tags, products or a category with Sentry Javascript Bugs: Typescript Best Practices (bretzel-app/crumbs, 127 stars), Connect Component To Figma (dequelabs/cauldron, 129 stars), Frontend UI (oomol-lab/open-flow, 223 stars) and Fork And Go (SimplePDF/simplepdf-embed, 407 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sentry Javascript Bugs?

getsentry (a GitHub organization, an official publisher) maintains it in getsentry/sentry, which has 45,495 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 7, 2026.

Source: getsentry/sentry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.