// Analyze Sentry issues, spans, crashes, and performance metrics. Use when user requests check in Sentry, asks about performance metrics and spans or asks about crash rates.
Provides coding standards for React Native — performance patterns, consistency rules, and clean React architecture. Use when writing, modifying, or reviewing code.
Records iOS/Android native MP4 evidence for test/repro flows extracted from an Expensify GitHub PR or issue. Use when the user asks to "record the flow for PR
Use when measuring a Sentry performance span locally with an agent-device replay flow on iOS simulator or Android emulator.
Drive iOS and Android devices for the Expensify App - testing, debugging, performance profiling, bug reproduction, and feature verification. Use when the developer needs to interact with the mobile app on a device.
Test the Expensify App using Playwright browser automation. Use when user requests browser testing, after making frontend changes, or when debugging UI issues
Onyx state management patterns — useOnyx hook, action files, optimistic updates, collections, and offline-first architecture. Use when working with Onyx connections, writing action files, debugging state, or implementing API calls with optimistic data.
| name | sentry |
| description | Analyze Sentry issues, spans, crashes, and performance metrics. Use when user requests check in Sentry, asks about performance metrics and spans or asks about crash rates. |
Use Sentry skill when:
The Sentry MCP server is configured in .mcp.json and gives Claude Code direct access to Sentry.
Setup (one-time per engineer): On first use, Claude Code will open a browser OAuth login to Sentry. Sign in and authorize — no manual token setup required.
Use these tools for data analysis:
| Tool | Purpose |
|---|---|
mcp__sentry__find_releases | Find release versions for scoping queries |
mcp__sentry__search_issues | Search for errors/crashes by query, project, date range |
mcp__sentry__search_events | Query raw events/spans (performance data, durations) |
mcp__sentry__search_issue_events | Get individual events for a known issue ID |
mcp__sentry__get_issue_tag_values | Inspect tag distributions (e.g. device, version) on an issue |
mcp__sentry__get_sentry_resource | Fetch a specific Sentry resource by URL/ID |
Do not use mcp__sentry__analyze_issue_with_seer — AI analysis is out of scope for this skill.
Always use:
expensifyapp