Ask Claude to Wire Up Sentry Error Tracking in Your Project
Setting up Sentry properly means more than just calling Sentry.init() — you need source maps, environment filtering, custom context, and release tracking all configured correctly. Claude can do it all in one go.
Tell Claude your stack and what you want:
Add Sentry to this Laravel + Vue 3 project.
- Use the latest Sentry SDK for both PHP and the frontend
- Capture authenticated user context on every error
- Filter out 404 and 401 errors from being reported
- Tag errors with the current release from the RELEASE env variable
- Add a test route that deliberately throws so I can verify it works
Claude will install the SDKs, write the bootstrap code, add the middleware (for PHP), configure the Vite plugin for source maps, and wire up user context from your auth system — all tailored to your actual codebase rather than the generic Sentry docs example.
For existing projects with a mix of caught and uncaught errors:
Review my error handling in @app/Exceptions/Handler.php and update it so
all unhandled exceptions are forwarded to Sentry with the current user context
and relevant request data attached as breadcrumbs.
Sentry setup is one of those tasks that takes two hours the first time and two minutes the second — let Claude skip you straight to minute two.
Log in to leave a comment.
The /security-review command scans your uncommitted changes for injection vectors, auth gaps, hardcoded secrets, and other common vulnerabilities.
The SessionStart hook fires when any session begins or resumes, making it ideal for loading environment variables and running one-time setup scripts.
Ask Claude to write property-based tests for your functions using fast-check — it identifies the mathematical invariants in your code and generates tests that cover inputs you'd never enumerate by hand.