Agent skill

Fix Sentry

by polarsource in polarsource/polar

Analyze and fix issues reported by Sentry in the Polar codebase.

Apache-2.0Auto-check passedData & Analytics

Install Fix Sentry

skills CLI
$ npx skills add polarsource/polar --skill fix-sentry -a claude-code

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

GitHub CLI
$ gh skill install polarsource/polar fix-sentry --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/polarsource/polar.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fix-sentry .claude/skills/fix-sentry && 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
fix-sentry
GitHub stars
10k
Token cost
~963 tokens
SKILL.md length
566 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
Apache-2.0

At a glance

Analyze and fix issues reported by Sentry in the Polar codebase.

  • Works in 4 steps: Analyze the Sentry issue → correlate with Logfire logs → Search source code → …
  • Tasks that involve DataFrames
  • SKILL.md covers Input, Step 1: Analyze the Sentry issue, Step 2: correlate with Logfire… and Step 3: Search source code, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Fix Sentry is an agent skill from polarsource/polar. Analyze and fix issues reported by Sentry in the Polar codebase.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Data & Analytics, covering DataFrames. It works with Sentry. The repository describes itself as: Polar — A billing platform for the intelligence era. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve DataFrames

Example prompts

  • “/fix-sentry”

Requirements

  • Pre-approved tools (allowed-tools): Bash(gh:*), Bash(git:*), logfire_polar*, sentry_polar*, github*

Workflow steps

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

  1. Analyze the Sentry issue
  2. correlate with Logfire logs
  3. Search source code
  4. Implement a fix

What it can do on your machine

Read from SKILL.md and the folder at commit 599c727. 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:

    • Bash(gh:*)
    • Bash(git:*)
    • logfire_polar*
    • sentry_polar*
    • github*

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    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

Fix Sentry loads about 963 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 566 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~963

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 passed

The automated check found no risky patterns in SKILL.md.

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

The full file from polarsource/polar at commit 599c727, republished under its Apache-2.0 licence (© polarsource). 566 words, ~963 tokens.

Download SKILL.mdSave it as .claude/skills/fix-sentry/SKILL.md (or your agent's skills folder).
name
fix-sentry
description
Analyze and fix issues reported by Sentry in the Polar codebase.
allowed-tools
Bash(gh:*), Bash(git:*), logfire_polar*, sentry_polar*, github*
user-invocable
true

You're responsible for analyzing and fixing issues reported by Sentry in the Polar codebase. This involves investigating the Sentry reports, identifying the root causes of the issues, and implementing fixes to resolve them.

Input

If not provided in the invocation prompt, you should ask the user for the a Sentry issue ID or a link to the Sentry issue. This will allow you to access the details of the issue and begin your analysis.

The Sentry organization ID of Polar is 4505046560538624 and its slug is polar-sh.

Step 1: Analyze the Sentry issue

Using the sentry_polar tools, access the details of the Sentry issue provided by the user. This includes the error message, stack trace, and any additional context or metadata associated with the issue.

Step 2: correlate with Logfire logs

Extract the correlation_id tag from the Sentry issue. If available, use it to search for related logs in Logfire using the logfire_polar tools. This can provide additional context and insights into the events leading up to the issue, helping you to further understand the root cause.

The clause will look like this: attributes->>'correlation_id' = '<correlation_id>'

If any logs has source_correlation_id, query those logs as well.

Step 3: Search source code

Look up for relevant code in the codebase using the information from the Sentry issue and the Logfire logs. This may involve searching for specific error messages, function names, or other relevant keywords in the codebase.

Step 4: Analyze findings

Synthetize the information gathered from the Sentry issue, Logfire logs, and source code search to formulate a hypothesis about the root cause of the issue.

Step 5: Implement a fix

Important: If your analysis indicates that the issue involves heavy architectural changes, or if you are unsure about the best way to implement a fix, do not proceed with implementing a fix on your own. Instead, open an issue on polarsource/polar with your findings and analysis.

Show full SKILL.md (250 more words)Show less
Step 5.1: Create a worktree

Always start by creating a git worktree for the work you are about to do. This will allow you to keep your changes organized and separate from the main codebase until they are ready to be merged. Run the following script:

bash
./dev/create-worktree <branch-name>

This will create a worktree and prepare the environment for you to work on the issue. Make sure to replace <branch-name> with a descriptive name for your branch, using only lowercase letters, digits, and underscores. The worktree is created in the ./worktrees directory, and you can navigate to it using cd ./worktrees/<branch-name>.

IMPORTANT: From now on, all your changes and commands should be executed within the context of the worktree you just created. This ensures that your changes are isolated and can be easily managed.

bash
cd ./worktrees/<branch-name>
Step 5.2: Implement a fix

Based on your analysis, implement a fix to resolve the issue. This may involve modifying existing code, adding new code, or making configuration changes.

Check linting, type checking, and tests before committing your changes, as detailed in AGENTS.md.

Step 5.3: Commit your changes

Commit your changes to the branch you created in the worktree. Make sure to write a clear and descriptive commit message that explains the changes you made and the reason for those changes.

Step 5.4: Open a pull request

Open a pull request on polarsource/polar using github tools, detailing your analysis, adding relevant links to the Sentry issue and Logfire logs, and describing the changes you made to fix the issue.

© polarsource, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/fix-sentry of polarsource/polar.

Open the folder on GitHubat commit 599c727

Compare with similar skills

Fix Sentry 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.

Fix Sentry compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix Sentry this skillpolarsource/polar10k—~963Automated safety check: PassApache-2.0
Chdb Datastorevemetric/vemetric3942 repos~1.4kAutomated safety check: PassApache-2.0
CSV Data Summarizercoffeefuelbump/csv-data-summarizer-claude-skill4682 repos~1.4kAutomated safety check: PassNone
Paper FiguresEvoScientist/EvoSkills4741 repos~4.4kAutomated safety check: PassApache-2.0
Python Executorcortega26/chile-hub1132 repos~1.5kAutomated safety check: PassMIT
DataframelyQuantco/dataframely618—~2.4kAutomated safety check: PassBSD-3-Clause

Similar skills

  • Chdb Datastore

    vemetric/vemetric

    A skill your agent uses when the user has tabular data (pandas DataFrame, parquet, csv, Arrow, json) and wants to filter, group, aggregate, join, or speed up slow pandas.

    394 GitHub starsUsed in 2 repos~1.4k tokens
    Data & AnalyticsAuto-check passed
  • CSV Data Summarizer

    coffeefuelbump/csv-data-summarizer-claude-skill

    Analyzes CSV files, generates summary stats, and plots quick visualizations using Python and pandas.

    468 GitHub starsUsed in 2 repos~1.4k tokens
    Data & AnalyticsAuto-check passed
  • Paper Figures

    EvoScientist/EvoSkills

    A skill your agent uses to produce standalone, publication-ready PNG graphics and reproducible matplotlib scripts from tabular data (CSVs or DataFrames).

    474 GitHub starsUsed in 1 repo~4.4k tokens
    Data & AnalyticsAuto-check passed
  • Python Executor

    cortega26/chile-hub

    Execute Python code in a safe sandboxed environment via [inference.sh](https://inference.sh).

    113 GitHub starsUsed in 2 repos~1.5k tokens
    Data & AnalyticsAuto-check passed
  • Dataframely

    Quantco/dataframely

    Best practices for polars data processing with dataframely. An agent skill from Quantco/dataframely.

    618 GitHub stars~2.4k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed
  • Retentioneering Product Analytics

    retentioneering/retentioneering-tools

    Analyze event logs, clickstreams, user paths, product funnels, retention, behavioral segments, transition graphs, step matrices, sequence patterns, and customer journeys using Retentioneering.

    920 GitHub stars~1.6k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed

More from polarsource/polar

All 18 skills in this repo
  • Polar Python SDK

    polarsource/polar

    Integrate Polar billing in server-side Python applications using the versioned Polar and PolarAsync clients.

    10k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Polar Typescript SDK

    polarsource/polar

    Integrate Polar billing in server-side TypeScript applications using the versioned createPolar and createPolarCore clients.

    10k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Adr Check

    polarsource/polar

    Check a code change against the repo's Accepted Architecture Decision Records (ADRs) in handbook/engineering/decisions/ and report violations with citations.

    10k GitHub stars~771 tokensUpdated today
    Auto-check passed
  • API Surface Review

    polarsource/polar

    Review changes to Polar's API contract — Pydantic schemas, FastAPI endpoints, OpenAPI output and the generated SDKs.

    10k GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Billing Review

    polarsource/polar

    Review a diff that touches Polar's billing domain — subscriptions, cycles and crons, orders, billing entries, meters and usage, discounts, checkout, payments and dunning, refunds, disputes, payouts…

    10k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Interview Task

    polarsource/polar

    Prepare an interview task for a candidate, as part of our hiring process.

    10k GitHub stars~933 tokensUpdated today
    Auto-check passed

Works with

Questions about Fix Sentry

What does Fix Sentry do?

Analyze and fix issues reported by Sentry in the Polar codebase. Fix Sentry is an agent skill from polarsource/polar. Analyze and fix issues reported by Sentry in the Polar codebase.

When should I use Fix Sentry?

Fix Sentry fits situations like: tasks that involve DataFrames.

How do I install Fix Sentry in Claude Code?

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

How do I install Fix Sentry in Codex?

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

Can I use Fix Sentry 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 polarsource/polar --skill fix-sentry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-sentry, .gemini/skills/fix-sentry, .github/skills/fix-sentry and .opencode/skills/fix-sentry in your project.

What does Fix Sentry need to run?

SKILL.md names no scripts, command-line tools or credentials: Fix Sentry is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(gh:*), Bash(git:*), logfire_polar*, sentry_polar*, github*.

Does Fix Sentry 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 Fix Sentry safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fix Sentry use?

Fix Sentry is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fix Sentry use?

About 963 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fix Sentry?

Skills that share tags, products or a category with Fix Sentry: Chdb Datastore (vemetric/vemetric, 394 stars), CSV Data Summarizer (coffeefuelbump/csv-data-summarizer-claude-skill, 468 stars), Paper Figures (EvoScientist/EvoSkills, 474 stars) and Python Executor (cortega26/chile-hub, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Sentry?

polarsource (a GitHub organization) maintains it in polarsource/polar, which has 10,336 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

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