fix-sentry

Solid

Auto-fix high-frequency Sentry issues: fetch issues > N occurrences, analyze stack traces, fix code, create GitHub issues, and submit PRs. Supports user feedback issues (event.type "default") with attachment analysis (logs, screenshots) when include_feedback=true. Use when: (1) User says "/fix-sentry", (2) User asks to fix Sentry issues.

AI & Automation 604 stars 115 forks Updated 3 days ago AGPL-3.0

Install

View on GitHub

Quality Score: 85/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Fix Sentry Skill Automated workflow: Sentry issues → analyze → fix → GitHub Issue → PR. **Announce at start:** "I'm using fix-sentry skill to find and fix high-frequency Sentry issues." ## Operating Modes ### Batch Mode (default) Invocation: `/fix-sentry` or `/fix-sentry threshold=50` - Uses the specified threshold (default 100) to fetch issues - Runs full Phase 1 → Phase 2 → Phase 3 - Fixes all qualifying issues ### Daemon Mode Invocation: `/fix-sentry limit=1` (from daemon script) - Phase 1 uses **adaptive threshold descent**: starts at 100, lowers progressively until a fixable issue is found - Fixes only 1 issue (controlled by `limit` parameter), then exits - If no fixable issue exists at any threshold → outputs `[NO_FIXABLE_ISSUES]` and exits ## Prerequisites - **Sentry MCP** must be configured (global or project scope) with `mcp__sentry__*` tools available - **gh CLI** must be authenticated - Working directory must be clean (`git status` shows no uncommitted changes) ## Workflow ### Phase 1: Collect & Filter Issues #### Step 1.1: Verify Environment ```bash git status --porcelain # must be clean git branch --show-current ``` If working directory is dirty, **STOP** and ask user to commit or stash first. #### Step 1.1b: Load Skip List (Daemon Mode Only) In daemon mode (`limit > 0`), load the skip list to avoid re-analyzing issues that were already triaged in previous sessions. The skip list is stored at: ``` ~/.wayland-fix-sentry/skip-list.json ``` F...

Details

Author
FerroxLabs
Repository
FerroxLabs/wayland
Created
3 months ago
Last Updated
3 days ago
Language
TypeScript
License
AGPL-3.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

fix-issues

Auto-fix GitHub issues labeled as bugs: fetch open bug issues, analyze feasibility, fix code, and submit PRs. One issue per invocation. Use when: (1) User says "/fix-issues", (2) User asks to fix GitHub issues.

604 Updated 3 days ago
FerroxLabs
AI & Automation Listed

sentry-fixer

Use when investigating or fixing a Sentry issue - fetches the issue and its latest event, maps the stacktrace onto the current working tree, checks whether the failing code still exists, produces a root-cause analysis and a fix plan, and implements the fix only after explicit user approval. Triggers on a Sentry issue URL, a short id like PROJ-4F2, a numeric issue id, "what's breaking in production", triaging the top errors, and post-release regression checks.

2 Updated 1 months ago
muhammetsafak
Code & Development Solid

debug-sentry-monitor

Monitor, triage, fix, and proactively enhance Sentry error monitoring for any project. Use when asked to: check Sentry, fix Sentry errors, triage Sentry issues, run post-deploy monitoring, review production errors, clean up Sentry noise, audit Sentry setup, improve monitoring coverage, enhance error tracking, or "run sentry check". Works with any GitHub repo — auto-detects org, project, framework, and config. Fetches issues via Sentry MCP, triages them, performs root cause analysis, fixes code bugs, updates noise filters, audits the monitoring architecture, and resolves issues only after verified fixes.

9 Updated yesterday
kensaurus