sentry
Skill0 starsChanged 27 days agoMITView on GitHub
Sentry pour Laravel 13 et Nuxt.js : error tracking, logs structurés, distributed tracing, profiling, source maps, alertes. Compatible avec Sentry cloud ou self-hosted (Rustrak). Utiliser quand on configure Sentry, on debug des erreurs, on met en place du monitoring, ou on optimise le tracing entre frontend et backend.
- Reads credentials
34 other projects use a version of this.
Adopted by
Most recently taken up by
- arfar-x/agent-skillstheir own version, first seen Nov 8, 2026
- Kangentic/kangentictheir own version, first seen Nov 7, 2026
- sgtlaugh/skillstheir own version, first seen Nov 1, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- ivanrvpereira/.agentstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use ghidra, datadog and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
mitsuhikoSkillghidra
Reverse engineer binaries using Ghidra's headless analyzer. Decompile executables, extract functions, strings, symbols, and analyze call graphs without GUI.
Also in 3 projects that use this
SentrySkilldatadog
Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.
Also in 4 projects that use this
xfstudioSkillfirebase
Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. I
Also in 3 projects that use this
mitsuhikoSkillopenscad
Create and render OpenSCAD 3D models. Generate preview images from multiple angles, extract customizable parameters, validate syntax, and export STL files for 3D printing platforms like MakerWorld.
Also in 3 projects that use this
digitalocean-labsSkillpostgres
Configure DigitalOcean Managed Postgres with bindable variables or schema isolation. Use when setting up databases, creating users, managing permissions, configuring multi-tenant schemas, or troubleshooting database connectivity on App Platform.
Also in 3 projects that use this
SentrySkillvercel
Deploy and inspect Vercel apps, assign aliases, delete deployments, investigate logs, and monitor deployment outcomes. Use for Vercel deployment and log requests, not GitHub code changes or other cloud providers.
Also in 3 projects that use this
- +2 more from mitsuhiko
Other versions34 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 34
- openai/skills★ 27ksame name
- anthropics/claude-quickstarts★ 19ksame name
- openai/plugins★ 7.8ksame name
- Expensify/App★ 5.1ksame name
- mitsuhiko/agent-commands★ 3.2ksame name
- mitsuhiko/agent-stuff★ 3.2ksame name
- chrisdoc/hevy-mcp★ 535same name
- wnzzer/rank-analysis★ 471same name
- getsentry/junior★ 409same name
- JetBrains/skills★ 386same name
24 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/laravel-core/templates/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- dokploy-deploySkill
- laravel-adminSkill
- laravel-aiSkill
- laravel-apiSkill
- laravel-coreSkill
- laravel-deploySkill
- laravel-inertiaSkill
- laravel-livewireSkill
- laravel-mcpSkill
- laravel-microserviceSkill
- laravel-multi-tenancySkill
- laravel-nuxtSkill
- laravel-performanceSkill
- laravel-queueSkill
- laravel-securitySkill
- laravel-testingSkill
- laravel-websocketSkill
- nuxt-coreSkill
- nuxt-uiSkill
- pestSkill
- project-definerSkill
- scribeSkill
- searxng-mcpSkill
- skill-creatorSkill
- skill-health-checkerSkill
- spatie-query-builderSkill
The file
Files
Sentry — Monitoring Laravel + Nuxt
Tu es un expert Sentry pour Laravel et Nuxt. Ton rôle est de configurer l'error tracking, les logs structurés, le distributed tracing, et le monitoring entre le backend Laravel et le frontend Nuxt.
Quand utiliser
- Configurer Sentry dans un projet Laravel ou Nuxt
- Debuguer des erreurs dans Sentry
- Mettre en place du distributed tracing
- Configurer les source maps pour les stack traces lisibles
- Ajouter des logs structurés vers Sentry
- Configurer des alertes
Quand NE PAS utiliser
- Monitoring purement infrastructure (Prometheus, Grafana)
- APM non-Sentry (Datadog, New Relic)
Architecture
Nuxt (Frontend) Laravel (Backend)
├── @sentry/nuxt ├── sentry/sentry-laravel
├── Source maps → Sentry ├── Logs → Sentry
├── Traces → Sentry ├── Traces → Sentry
└── Replay (optionnel) └── Profiling (optionnel)
│ │
└────────── Sentry ────────────┘
(cloud ou Rustrak)1. Laravel — Installation
composer require sentry/sentry-laravel
php artisan sentry:publish --dsn=https://<key>@o<orgId>.ingest.sentry.io/<projectId>bootstrap/app.php
<?php
use Illuminate\Foundation\Application;
use Illuminate\Foundation\Configuration\Exceptions;
use Illuminate\Foundation\Configuration\Middleware;
use Sentry\Laravel\Integration;
return Application::configure(basePath: dirname(__DIR__))
->withRouting(
web: __DIR__.'/../routes/web.php',
api: __DIR__.'/../routes/api.php',
commands: __DIR__.'/../routes/console.php',
health: '/up',
)
->withMiddleware(function (Middleware $middleware) {
//
})
->withExceptions(function (Exceptions $exceptions) {
Integration::handles($exceptions);
})
->create();.env
SENTRY_LARAVEL_DSN=https://<key>@o<orgId>.ingest.sentry.io/<projectId>
SENTRY_TRACES_SAMPLE_RATE=1.0
SENTRY_ENABLE_LOGS=true
SENTRY_LOG_LEVEL=warning2. Laravel — Logs structurés
# .env
LOG_CHANNEL=stack
LOG_STACK=single,sentry_logs
SENTRY_ENABLE_LOGS=true
SENTRY_LOG_LEVEL=warningUsage
use Illuminate\Support\Facades\Log;
// Log standard (va dans Sentry via le stack)
Log::info('Commande traitée', ['order_id' => $order->id]);
// Log directement vers Sentry
Log::channel('sentry_logs')->error('Échec paiement', [
'user_id' => $user->id,
'amount' => $amount,
]);Best practices logs
// ✅ Wide event avec contexte
Log::info('Checkout complété', [
'order_id' => $order->id,
'user_id' => $user->id,
'cart_value' => $cart->total,
'payment_method' => 'stripe',
'duration_ms' => $duration,
]);
// ❌ Scattered thin logs
Log::info('Début checkout');
Log::info('Validation panier');
Log::info('Paiement traité');3. Laravel — Tracing
# .env
SENTRY_TRACES_SAMPLE_RATE=1.0 # 100% en dev, réduire en prodDistributed tracing vers Nuxt
{{-- resources/views/app.blade.php --}}
<head>
{!! \Sentry\Laravel\Integration::sentryMeta() !!}
</head>Cela injecte les meta tags sentry-trace et baggage pour connecter
le trace du backend au frontend.
Custom instrumentation
use Sentry\Tracing\SpanContext;
$parentSpan = \Sentry\SentrySdk::getCurrentHub()->getSpan();
if ($parentSpan !== null) {
$context = SpanContext::make()
->setDescription('Processus commande')
->setOp('commerce.order');
$span = $parentSpan->startChild($context);
\Sentry\SentrySdk::getCurrentHub()->setSpan($span);
// Votre logique...
$span->finish();
\Sentry\SentrySdk::getCurrentHub()->setSpan($parentSpan);
}4. Laravel — Breadcrumbs
use Sentry\Breadcrumb;
\Sentry\addBreadcrumb(
category: 'auth',
message: 'Utilisateur connecté',
metadata: ['user_id' => $userId],
level: Breadcrumb::LEVEL_INFO,
);5. Laravel — Enrichir les erreurs
User context
// Middleware
\Sentry\configureScope(function (\Sentry\State\Scope $scope) use ($user): void {
$scope->setUser([
'id' => $user->id,
'email' => $user->email,
]);
});Tags
\Sentry\configureScope(function (\Sentry\State\Scope $scope): void {
$scope->setTag('page.locale', 'fr-fr');
$scope->setTag('feature', 'checkout');
});6. Nuxt — Installation
npx nuxi@latest module add sentrynuxt.config.ts
export default defineNuxtConfig({
modules: ['@sentry/nuxt/module'],
sentry: {
dsn: 'https://<key>@o<orgId>.ingest.sentry.io/<projectId>',
tracesSampleRate: 1.0,
replaysSessionSampleRate: 0.1,
replaysOnErrorSampleRate: 1.0,
},
})Sentry client config
// sentry.client.config.ts
import * as Sentry from "@sentry/nuxt";
Sentry.init({
dsn: "https://<key>@o<orgId>.ingest.sentry.io/<projectId>",
tracesSampleRate: 1.0,
// Optionnel : Session Replay
replaysSessionSampleRate: 0.1,
replaysOnErrorSampleRate: 1.0,
});Sentry server config
// sentry.server.config.ts
import * as Sentry from "@sentry/nuxt";
Sentry.init({
dsn: "https://<key>@o<orgId>.ingest.sentry.io/<projectId>",
tracesSampleRate: 1.0,
});7. Nuxt — Source maps
// nuxt.config.ts
export default defineNuxtConfig({
sentry: {
sourceMapsLoaderOptions: {
// Supprimer les source maps après upload
deleteSourcemapsAfterUpload: true,
},
},
})Pour Rustrak (self-hosted), configurer le plugin Vite :
// nuxt.config.ts
import { sentryVitePlugin } from "@sentry/vite-plugin";
export default defineNuxtConfig({
vite: {
plugins: [
sentryVitePlugin({
org: "anything", // ignoré par Rustrak
project: "my-project", // doit matcher le slug Rustrak
authToken: process.env.SENTRY_AUTH_TOKEN,
url: process.env.SENTRY_URL, // URL de Rustrak
sourcemaps: {
filesToDeleteAfterUpload: ["./**/*.map"],
},
}),
],
},
})8. Nuxt — Logs structurés
// Dans un composable ou page
const { logger } = useSentryLogger();
logger.info("Utilisateur connecté", {
userId: user.id,
plan: user.plan,
});
logger.error("Paiement échoué", {
orderId: order.id,
reason: "card_declined",
});9. Nuxt — Error handling
// app.vue ou error.vue
<script setup lang="ts">
import * as Sentry from "@sentry/nuxt";
const error = useError();
if (error.value) {
Sentry.captureException(error.value);
}
</script>10. Rustrak (Self-hosted)
Si vous utilisez Rustrak au lieu de Sentry cloud :
Laravel
SENTRY_LARAVEL_DSN=http://<key>@<rustrak-host>:8080/<projectId>Nuxt
Sentry.init({
dsn: "http://<key>@<rustrak-host>:8080/<projectId>",
// Pas de tunnel nécessaire, Rustrak accepte les CORS
})Source maps vers Rustrak
# .env
SENTRY_AUTH_TOKEN=<token-rustrak>
SENTRY_URL=http://<rustrak-host>:808011. Features Rustrak
Rustrak est compatible avec les SDKs Sentry mais ne supporte pas :
- Performance monitoring (transactions, spans) — en dehors des erreurs
- Session Replay
- Release management
- Profiling
Pour ces features, utiliser Sentry cloud.
Bonnes pratiques
- DSN dans .env — Jamais en dur dans le code
- Sample rate — 100% en dev, réduire en prod (0.1-0.5)
- Source maps — Toujours upload pour les stack traces lisibles
- Distributed tracing — Meta tags Laravel → Nuxt pour connecter les traces
- Logs structurés — Wide events avec contexte, pas de thin logs
- User context — Setter l'utilisateur pour le debugging
- Tags — Filtrer par environment, feature, etc.
- Breadcrumbs — Ajouter du contexte avant les erreurs
- before_send — Filtrer les erreurs non pertinentes
- CORS — Autoriser
sentry-traceetbaggageheaders
Checklist setup
Laravel
sentry/sentry-laravelinstallé- DSN configuré dans
.env - Exceptions handler configuré (
Integration::handles()) - Logs channel
sentry_logsconfiguré - Tracing sample rate défini
- Meta tags pour distributed tracing
Nuxt
@sentry/nuxtinstallé- Module ajouté à
nuxt.config.ts - Client + server config créés
- Source maps upload configurés
- Tracing sample rate défini
- CORS headers autorisés (si Laravel séparé)
Cross-références
laravel-core— Fondamentaux Laravellaravel-security— Sécuritélaravel-performance— Performancenuxt-core— Fondamentaux Nuxtlaravel-nuxt— API Laravel pour Nuxt
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

