error-tracking
Implement error tracking with Sentry for automatic exception monitoring, release tracking, and performance issues. Use when setting up error monitoring, tracking bugs in production, or analyzing application stability.
How do I install this agent skill?
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill error-trackingIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides templates and reference guides for Sentry error tracking. Security analysis identified that the example code in the Express and Python reference guides contains SQL injection vulnerabilities, as user-controlled parameters are directly interpolated into database queries. The skill correctly uses environment variables for sensitive configuration like DSNs and Auth Tokens.
- Socketwarn
2 alerts: gptSecurity
- Snykpass
Risk: LOW · No issues
- Runlayerfail
6/11 files flagged
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Error Tracking
Table of Contents
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 -d
Reference 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
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/aj-geddes/useful-ai-prompts/error-tracking">View error-tracking on skillZs</a>