fix-sentry
Best for Teams using Sentry for erro…Works with GitHub
⌘source
- author
@iOfficeAI- repo
- iOfficeAI/AionUi
- language
- TypeScript
★22kstars
1.9kforks
Apr 19, 2026
✦overview.md
Key Features
- ·Automatically fetches high-frequency Sentry issues
- ·Analyzes stack traces and user feedback attachments
- ·Creates GitHub issues and submits pull requests
- ·Supports batch processing and single-issue daemon modes
- ·Requires pre-configured Sentry MCP and authenticated gh CLI
Use Cases
- →Automating the triage and fix of recurring production errors reported in Sentry
- →Running a scheduled daemon to proactively fix the most frequent issues
- →Responding to a user command to fix Sentry issues with a single slash command
Best for
- ✓Teams using Sentry for error monitoring
- ✓CI/CD pipelines needing automated bug fixes
Not ideal for
- !One-off debugging of unique, low-frequency errors
- !Environments without Sentry MCP or GitHub CLI setup
FAQs
name
fix-sentry
description
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.
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
limitparameter), 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 statusshows no uncommitted changes)
Workflow
Phase 1: Collect & Filter Issues
Step 1.1: Verify Environment
git status --porcelain # must be clean
git branch --show-current
$install
1-click copynpx skills add iOfficeAI/AionUi --skill fix-sentrySafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.