New: 98,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

Agent skill

Sentry Fix

by different-ai-studio in different-ai-studio/teamclu

A skill your agent uses when the user wants to fix a Sentry issue, auto-repair a bug from Sentry, or create a fix PR for a Sentry error.

MITAuto-check passedMobile

Install Sentry Fix

skills CLI
$ npx skills add different-ai-studio/teamclu --skill sentry-fix -a claude-code

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

GitHub CLI
$ gh skill install different-ai-studio/teamclu sentry-fix --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/different-ai-studio/teamclu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/sentry-fix .claude/skills/sentry-fix && 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-fix
GitHub stars
167
Token cost
~2.2k tokens
SKILL.md length
1,132 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user wants to fix a Sentry issue, auto-repair a bug from Sentry, or create a fix PR for a Sentry error.

  • Works in 6 steps: Gather Context → Confirm with User → Implement Fix → …
  • The user wants to fix a Sentry issue
  • SKILL.md covers Arguments, Projects, Execution Steps and Constraints
  • Calls pnpm, git and gh

What it does

Sentry Fix is an agent skill from different-ai-studio/teamclu. Use when the user wants to fix a Sentry issue, auto-repair a bug from Sentry, or create a fix PR for a Sentry error. Triggers on "修复 sentry", "fix sentry issue", "sentry 修复", "sentry fix".

Its SKILL.md is about 2.2k 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 Mobile. It works with Sentry, Rust, pnpm and Expo. The repository describes itself as: TeamClu, AI Agent Desktop Workspace. The licence is MIT.

When your agent uses it

  • The user wants to fix a Sentry issue
  • Auto-repair a bug from Sentry
  • Create a fix PR for a Sentry error
  • Fix sentry issue

Example prompts

  • “修复 sentry”
  • “fix sentry issue”
  • “sentry 修复”
  • “/sentry-fix”

Workflow steps

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

  1. Gather Context
  2. Confirm with User
  3. Implement Fix
  4. Verify
  5. Commit, then stop
  6. PR — only when the user asks

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • git
    • gh
    • cargo
    • node

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, git and gh, which can reach the network depending on how they are called.

    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 Fix loads about 2.2k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 1,132 words of instructions outside code blocks.

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

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 different-ai-studio/teamclu at commit e4ff421, republished under its MIT licence (© different-ai-studio). 1,132 words, ~2,186 tokens.

Download SKILL.mdSave it as .claude/skills/sentry-fix/SKILL.md (or your agent's skills folder).
name
sentry-fix
description
Use when the user wants to fix a Sentry issue, auto-repair a bug from Sentry, or create a fix PR for a Sentry error. Triggers on "修复 sentry", "fix sentry issue", "sentry 修复", "sentry fix".

Sentry Fix — Auto-Fix Issue with Test

Fix a specific Sentry issue: gather context, confirm with user, implement fix, write regression test, verify, commit.

Arguments

  • <ISSUE-ID> (required): Sentry issue short ID, e.g. TEAMCLU-REACT-7Q

The issue ID is passed as the skill argument: /sentry-fix TEAMCLU-REACT-7Q

Projects

Route on the issue ID prefix. Every project's short ID carries its own segment, so the prefix alone identifies the codebase:

PrefixSentry SlugCodeTestLint / typecheck
TEAMCLU-REACT-ucar-inc/teamclu-reactpackages/app/pnpm test:unitpnpm typecheck && pnpm lint
TEAMCLU-RUST-ucar-inc/teamclu-rustapps/desktop/see Rust tests belowpnpm rust:clippy
TEAMCLU-IOS-ucar-inc/teamclu-iosapps/ios/pnpm ios:test:core—
TEAMCLU-EXPO-ucar-inc/teamclu-expoapps/expo/pnpm expo:testpnpm typecheck:expo

ucar-inc/teamclu (a bare TEAMCLU- prefix with no platform segment) is the old, deleted project. An issue ID in that shape is from before 2026-09-04 and cannot be fetched; ask the user for a current one.

teamclu-react covers both the web app and the desktop webview — the desktop Rust process reports separately under teamclu-rust.

Rust tests

Do not run bare cargo test. It exits 101 on teamclu-introspect sidecar binary not found: check/clippy are analysis paths, but test is a real build and runs apps/desktop/build.rs, which panics when binaries/ (entirely gitignored) has no sidecar and CI is unset.

Main checkout — the wrapper builds the sidecar first:

bash
node scripts/rust-cli.js test --manifest-path apps/desktop/Cargo.toml --lib <filter>

Fresh worktree — CI=1 alone is not enough, because tauri-build still globs bundle.resources paths that do not exist there:

bash
CI=1 TAURI_CONFIG='{"bundle":{"externalBin":[],"resources":[]}}' \
  node scripts/rust-cli.js test --manifest-path apps/desktop/Cargo.toml --lib <filter>

Always go through pnpm rust:* / scripts/rust-cli.js rather than bare cargo — bare cargo clippy fails on a fresh checkout for the same reason.

Execution Steps

Phase 1: Gather Context
  1. Fetch issue details with stack trace. issue view resolves a short ID across projects, so no slug is needed:
bash
sentry issue view <ISSUE-ID> --json

This is also the only place volume numbers come from — count, userCount, firstSeen and lastSeen are silently dropped from issue list --fields on CLI 0.26.1.

  1. From the stack trace and error message, identify the relevant source files and functions in the codebase.

  2. Read those source files to understand the code context around the error site.

  3. Perform local root cause analysis. Produce a clear root cause summary.

Two checks worth making before writing it up:

  • Is this one of several groups for the same defect? A sourcemapped build and a minified one group separately. Search sibling issues for the same metadata.value; if they match, one fix closes all of them, and the plan should say so.
  • Is there a group with a sourcemapped frame? Prefer analyzing the one whose culprit is a repo path (/src/...) over a bundle (assets/index-*.js) — it names the file directly instead of needing to be reverse-engineered.

If the stack trace is insufficient to identify the root cause: Stop and ask the user for additional context. Do NOT guess.

Phase 2: Confirm with User

Present a fix plan in the terminal. It MUST include:

  1. Root cause — one paragraph from local analysis
  2. Files to modify — exact paths and what changes in each
  3. Proposed fix — description of the code changes
  4. Regression test plan — what test is added and what it verifies
  5. Verification commands — which commands will be run

STOP HERE and wait for user confirmation. Do NOT proceed until the user says yes. This applies even when the root cause looks obvious.

Phase 3: Implement Fix
  1. Branch. Never work on main (see the Git Workflow section of CLAUDE.md):
bash
git checkout -b sentry-fix/<issue-id-lowercase>

This checkout is often shared with other sessions. Before branching, run git status --short and confirm the tree is clean — a dirty tree means someone else's work in progress, and carrying it onto your branch (or committing it) has happened before. Never git reset --hard here.

  1. Implement the fix:

    • Follow existing code patterns and style
    • Only modify files directly related to the issue
    • No gratuitous refactoring

  2. Write a regression test:

    • Rust: #[test] in the relevant module's test section, or a test file in the same directory.
    • React / Expo: a vitest test in the corresponding .test.ts(x), creating one if none exists and following neighbouring test files.
    • iOS: a SwiftPM test under apps/ios/Packages/AMUXCore/Tests/.

    The test must reproduce the scenario that caused the original error.

  3. Prove the test catches the bug. Stash or revert the fix, run the new test, and confirm it fails for the expected reason; then restore the fix and confirm it passes. A regression test that was never seen red is not evidence. Use a file copy plus git checkout -- <path> rather than git stash on a shared checkout.

Show full SKILL.md (400 more words)Show less
Phase 4: Verify

Run the full suite for the platform, including the test just written — not just the linter:

  • React: pnpm test:unit && pnpm typecheck && pnpm lint
  • Rust: the rust-cli.js test command above, plus pnpm rust:clippy and cargo fmt --check --manifest-path apps/desktop/Cargo.toml
  • Expo: pnpm expo:test && pnpm typecheck:expo
  • iOS: pnpm ios:test:core (pnpm ios:test additionally needs a booted simulator; skip it unless the fix is UI-level and say that you did)

Never pipe these through tail/head when you care about the result — the pipeline's exit code is the pager's, so a failure reads as exit 0. Redirect to a file and check $?.

Compare lint output against the pre-change baseline rather than counting warnings in the absolute: this repo carries known warnings, and "0 errors" with an unchanged warning set is the bar.

If verification fails:

  1. Read the error output
  2. Fix the issue
  3. Re-run verification
  4. Maximum 2 retry rounds. If still failing, stop and report to the user.

If a failure looks unrelated to the change, check it against the known-flaky and known-broken memories before assuming you caused it — several suites in this repo fail on a clean main for environmental reasons.

Phase 5: Commit, then stop
  1. Stage only the files you changed, by explicit path. Never git add -A — an unscoped add on this shared checkout is what put a private document into a public commit once already:
bash
git add <changed-files>
git commit -m "fix(<scope>): <description> (Sentry <ISSUE-ID>)"

<scope> is the module/component (e.g. chat, settings, daemon, editor).

  1. Stop here and report back. Per CLAUDE.md, do not git push or run gh pr create on your own initiative, even when everything is green. Wait for an explicit "open the PR" / "ship it" / "提 PR" / "可以提 PR 了".

Report: what was fixed, the verification results (including the red-then-green evidence for the regression test), and anything left unverified.

Phase 6: PR — only when the user asks
bash
git push -u origin sentry-fix/<issue-id-lowercase>
gh pr create --title "fix(<scope>): <short description>" --body "$(cat <<'PREOF'
## Sentry Issue

Fixes [<ISSUE-ID>](<sentry-issue-permalink>)

## Root Cause

<root cause summary from local analysis>

## Fix

<description of code changes>

## Test Coverage

<the regression test, and the failure it produces without the fix>

## Verification

<commands run and their results; name anything not verified and why>
PREOF
)"

State verification honestly in the PR body — if something could not be run, say which and why rather than omitting it.

Constraints

  • NEVER modify code before the user confirms the fix plan (Phase 2)
  • NEVER modify files unrelated to the issue
  • ALWAYS write a regression test, and always see it fail before it passes
  • NEVER push or open a PR without an explicit request (Phase 5/6)
  • If sentry CLI is not authenticated, prompt the user to run sentry auth login
  • If gh CLI is not authenticated, prompt the user to run gh auth login

© different-ai-studio, MIT. 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 .claude/skills/sentry-fix of different-ai-studio/teamclu.

Open the folder on GitHubat commit e4ff421

Compare with similar skills

Sentry Fix 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 Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sentry Fix this skilldifferent-ai-studio/teamclu167—~2.2kAutomated safety check: PassMIT
Screenmapaleqsio/screenmap242—~7.2kAutomated safety check: PassMIT
Mobile Nativeleepokai/Codync1771 repos~4.2kAutomated safety check: PassMIT
ThemingCode-with-Beto/skills141—~2.5kAutomated safety check: PassNone
Add Error Trackinggotempsh/temps826—~4.2kAutomated safety check: NotesApache-2.0
Expo UIsickn33/agentic-awesome-skills47k1 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Screenmap

    aleqsio/screenmap

    Generate a visual navigation map of an Expo / React Native or NativeScript app.

    242 GitHub stars~7.2k tokensUpdated 4 days ago
    MobileAuto-check passed

  • Mobile Native

    leepokai/Codync

    Make a web app feel native on a phone — the small CSS and meta-tag fixes that separate "a website in a browser" from something that feels installed.

    177 GitHub starsUsed in 1 repo~4.2k tokens
    MobileAuto-check passed

  • Theming

    Code-with-Beto/skills

    Scaffold a unified, cross-platform color theme system into an Expo Router app.

    141 GitHub stars~2.5k tokensUpdated 2 mo ago
    MobileAuto-check passed

  • Add Error Tracking

    gotempsh/temps

    Add Temps error tracking to applications using the Sentry-compatible SDK.

    826 GitHub stars~4.2k tokensUpdated yesterday
    MobileAuto-check: notes

  • Expo UI

    sickn33/agentic-awesome-skills

    Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android rendered from React in an Expo or React Native app.

    47k GitHub starsUsed in 1 repo~1.1k tokens
    MobileAuto-check passed

  • Fishjam React Native Client

    software-mansion-labs/skills

    React Native / Expo SDK for Fishjam — video/audio streaming on iOS and Android.

    291 GitHub stars~1.9k tokensUpdated 10 days ago
    MobileAuto-check passed

More from different-ai-studio/teamclu

All 8 skills in this repo

  • App Auth

    different-ai-studio/teamclu

    A skill your agent uses when implementing TeamClu platform sign-in, organization-role access, employee pages or protected data endpoints in an app, or changing its login permissions.

    167 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Create Role

    different-ai-studio/teamclu

    Create a workspace role that follows the ROLE.md specification.

    167 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Image Gen

    different-ai-studio/teamclu

    生成图片：配图、插图、海报、头像、示意图、Logo 草稿、封面、banner。触发词：画一张、画个、生成图片、生成一张图、做张图、做个图、配图、出图、生图、AI 绘图、image、draw、illustration、poster。仅从零生成，不做已有图片的编辑或修改。

    167 GitHub stars~430 tokensUpdated yesterday
    Auto-check passed

  • macOS Control

    different-ai-studio/teamclu

    Control macOS desktop applications: open/operate apps, click buttons, type text, scroll, keyboard shortcuts, window management, toggle options, dropdown selections, etc.

    167 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed

  • Sentry Monitor

    different-ai-studio/teamclu

    A skill your agent uses when the user wants to check Sentry issues, run a Sentry daily report, or monitor error trends.

    167 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Windows Control

    different-ai-studio/teamclu

    Control Windows desktop applications: open/operate apps, click controls, type text, scroll, keyboard shortcuts, window management, toggle options, lists and combos, etc.

    167 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Sentry Fix

What does Sentry Fix do?

A skill your agent uses when the user wants to fix a Sentry issue, auto-repair a bug from Sentry, or create a fix PR for a Sentry error. Sentry Fix is an agent skill from different-ai-studio/teamclu. Use when the user wants to fix a Sentry issue, auto-repair a bug from Sentry, or create a fix PR for a Sentry error.

When should I use Sentry Fix?

Sentry Fix fits situations like: the user wants to fix a Sentry issue; auto-repair a bug from Sentry; create a fix PR for a Sentry error; fix sentry issue.

How do I install Sentry Fix in Claude Code?

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

How do I install Sentry Fix in Codex?

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

Can I use Sentry Fix 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 different-ai-studio/teamclu --skill sentry-fix -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-fix, .gemini/skills/sentry-fix, .github/skills/sentry-fix and .opencode/skills/sentry-fix in your project.

What does Sentry Fix need to run?

Going by SKILL.md and its folder, Sentry Fix needs the command-line tools its instructions call (pnpm, git, gh, cargo and node).

Does Sentry Fix access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Sentry Fix 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 Sentry Fix use?

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

How many tokens does Sentry Fix use?

About 2.2k tokens (SKILL.md is roughly 8.7k 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 Sentry Fix?

Skills that share tags, products or a category with Sentry Fix: Screenmap (aleqsio/screenmap, 242 stars), Mobile Native (leepokai/Codync, 177 stars), Theming (Code-with-Beto/skills, 141 stars) and Add Error Tracking (gotempsh/temps, 826 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sentry Fix?

different-ai-studio (a GitHub organization) maintains it in different-ai-studio/teamclu, which has 167 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.

Source: different-ai-studio/teamclu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.