Sentry Auditing Skill
Proactive error analysis and issue tracking for the SkullRender ecosystem.
Core Mandates
- Correlation First: Always correlate Sentry issues with local file paths and Git history when analyzing.
- Impact Analysis: Prioritize issues based on frequency, user impact, and proximity to critical "Bones" (Security/Core).
- Contextual Debugging: Use the
list_issuesandget_issuetools to fetch event tags and breadcrumbs before proposing a fix.
Tool Usage Standards
sentry.list_issues
- Use filters like
is:unresolvedto narrow down relevant audits. - Map the
projectslug correctly from the centralized configuration.
sentry.get_event
- Analyze the
stacktraceto find exact lines in the local repository. - Cross-reference with
FileSystemskill to read the offending code.
Troubleshooting
- OAuth Errors: Sentry via
mcp-remoterequires a valid Personal Access Token withevent:read,issue:read, andproject:read. - Project Slugs: Ensure the project slug matches exactly what is configured in
mcp_config.py.