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.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.