Specification
- Skill ID
- aj-geddes/useful-ai-prompts/error-tracking
- Publisher
- aj-geddes
- Repository
- useful-ai-prompts
- Installs
- 0
- Files
- 9
- Synced
- Sep 23, 2026
How to use it
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
aj-geddes/useful-ai-prompts/error-trackingInstalls these files- SKILL.md
- references/custom-error-context.md
- references/express-middleware-integration.md
- references/performance-monitoring.md
- references/python-sentry-integration.md
- references/sentry-setup.md
- references/source-maps-and-release-management.md
- scripts/validate-api.sh
- templates/api-scaffold.yaml
What this skill tells the agent
Error Tracking
Table of Contents
- Overview
- When to Use
- Quick Start
- Reference Guides
- Best Practices
Overview
Set up comprehensive error tracking with Sentry to automatically capture, report, and analyze exceptions, performance issues, and application stability.
When to Use
- Production error monitoring
- Automatic exception capture
- Release tracking
- Performance issue detection
- User impact analysis
Quick Start
Minimal working example:
npm install -g @sentry/cli
npm install @sentry/node @sentry/tracing
sentry init -dReference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Sentry Setup | Sentry Setup, Node.js Sentry Integration |
| Express Middleware Integration | Express Middleware Integration |
| Python Sentry Integration | Python Sentry Integration |
| Source Maps and Release Management | Source Maps and Release Management, CI/CD Release Creation |
| Custom Error Context | Custom Error Context |
| Performance Monitoring | Performance Monitoring |
Best Practices
✅ DO
- Set up source maps for production
- Configure appropriate sample rates
- Track releases and deployments
- Filter sensitive information
- Add meaningful context to errors
- Use breadcrumbs for debugging
- Set user information
- Review error patterns regularly
❌ DON'T
- Send 100% of errors in production
- Include passwords in context
- Ignore configuration for environment
- Skip source map uploads
- Log personally identifiable information
- Use without proper filtering
- Disable tracking in production
More from aj-geddes
Use this skill in a project
Open any RiverX project, search the Skills panel for aj-geddes/useful-ai-prompts/error-tracking, and install it in one click.