error-monitoring
Generates protocol-based error/crash monitoring with swappable providers (Sentry, Crashlytics). Use when user wants to add crash reporting, error tracking, or production monitoring.
npx skills add rshankras/claude-code-apple-skills --skill error-monitoring --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Error Monitoring Generator Generates a production-ready error monitoring infrastructure with protocol-based architecture for easy provider swapping. ## When This Skill Activates - User asks to "add crash reporting" or "error monitoring" - User mentions "Sentry", "Crashlytics", or "crash analytics" - User wants to "track errors in production" - User asks about "debugging production issues" ## Pre-Generation Checks (CRITICAL) ### 1. Project Context Detection Before generating, ALWAYS check: ```bash # Check for existing crash reporting rg -l "Sentry|Crashlytics|CrashReporter" --type swift # Check Package.swift for existing SDKs cat Package.swift | grep -i "sentry\|firebase\|crashlytics" # Check for existing error handling patterns rg "captureError|recordError|logError" --type swift | head -5 ``` ### 2. Conflict Detection If existing crash reporting found: - Ask: Replace, wrap existing, or create parallel system? ## Configuration Questions Ask user via AskUserQuestion: 1. **Initial provider?** - Sentry (recommended for indie devs) - Firebase Crashlytics (if already using Firebase) - None (set up infrastructure only) 2. **Include breadcrumbs?** - Yes (track navigation, user actions) -
- When This Skill Activates
- Pre-Generation Checks (CRITICAL)
- 1. Project Context Detection
- 2. Conflict Detection
- Configuration Questions
- Generation Process
- Step 1: Create Core Files
- Step 2: Read Templates
- Step 3: Customize for Project
- Step 4: Integration
- Provider Setup
- Sentry
- Firebase Crashlytics
- Generated Code Patterns
Check for existing crash reporting rg -l "Sentry|Crashlytics|CrashReporter" --type swift Check Package.swift for existing SDKs cat Package.swift | grep -i "sentry\|firebase\|crashlytics" Check for existing error handling patterns rg "captureError|recordError|logError" --type swift | head -5
What does the error-monitoring skill do?
Generates protocol-based error/crash monitoring with swappable providers (Sentry, Crashlytics). Use when user wants to add crash reporting, error tracking, or production monitoring.
How do I install it?
Run `npx skills add rshankras/claude-code-apple-skills --skill error-monitoring --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rshankras/claude-code-apple-skills, a repository with 589 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.