メニュー
Sentry error tracking setup. Use when installing the Sentry SDK, fixing hardcoded DSNs, or adding source map upload for frontend, Next.js, Node, or Python.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/laurigates/claude-plugins --skill configure-sentryコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-07-05T00:00:00.000Z" |
| reviewed | "2026-07-05T00:00:00.000Z" |
| description | Sentry error tracking setup. Use when installing the Sentry SDK, fixing hardcoded DSNs, or adding source map upload for frontend, Next.js, Node, or Python. |
| allowed-tools | Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite, WebSearch, WebFetch |
| args | [--check-only] [--fix] [--type <frontend|nextjs|python|node>] |
| argument-hint | [--check-only] [--fix] [--type <frontend|nextjs|python|node>] |
| name | configure-sentry |
Check and configure Sentry error tracking integration against project standards.
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up Sentry error tracking for a new project | Debugging a specific Sentry issue or alert (use Sentry MCP server) |
| Sentry-specific setup and compliance in depth | Wiring up the whole observability stack — OTel traces/metrics + logging (use /configure:instrumentation, which delegates Sentry gaps back here) |
| Checking Sentry SDK installation and configuration compliance | Querying Sentry events or performance data (use Sentry API/MCP) |
| Fixing hardcoded DSNs or missing environment variable references | Managing Sentry project settings in the Sentry dashboard |
| Adding source map upload and release tracking to CI/CD | Configuring Sentry alerting rules or notification channels |
| Verifying Sentry configuration across frontend, Next.js, Node.js, or Python projects | Installing a different error tracking tool (e.g., Bugsnag, Rollbar) |
| Adding profiling, structured logging, or enrichment helpers | Configuring Sentry alerting rules or notification channels |
| Project-level setup and compliance auditing | Day-to-day SDK usage patterns — spans, breadcrumbs, cron monitoring, replay (use typescript-plugin:typescript-sentry) |
find . -maxdepth 1 -name \'package.json\'find . -maxdepth 1 -name \'pyproject.toml\'find . -maxdepth 1 -name \'requirements.txt\'find . -maxdepth 1 -name '.project-standards.yaml' -type ffind . -maxdepth 1 -name 'package.json' -exec grep -o '"@sentry/[^"]*"' {} +find . -maxdepth 1 -name 'pyproject.toml' -exec grep 'sentry' {} +find . -maxdepth 3 -name "*sentry*" -type ffind . -maxdepth 1 -name 'next.config.*'find . -path '*/src/*' -maxdepth 2 -name 'instrumentation*' -type ffind . \( -name '.env*' -o -path '*/.github/workflows/*' \) -type f -exec grep -l 'SENTRY_DSN' {} +find . -path '*/.github/workflows/*' -maxdepth 3 -name '*.yml'Skills referenced: sentry (MCP server for Sentry API)
Parse these from $ARGUMENTS:
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply all fixes automatically without prompting |
--type <type> | Override project type detection (frontend, nextjs, python, node) |
CRITICAL: Before configuring Sentry SDKs, verify latest versions:
Use WebSearch or WebFetch to verify current SDK versions before configuring Sentry.
Execute this Sentry compliance check:
Determine the project type to select the appropriate SDK and configuration:
.project-standards.yaml for project_type fieldpackage.json with next dependency (check for @sentry/nextjs)package.json with vue/react dependencies (without Next.js)package.json with Node.js backend (express, fastify, etc.)pyproject.toml or requirements.txt--type flag is provided, use that value insteadCheck for Sentry SDK based on detected project type:
Next.js:
@sentry/nextjs in package.json dependencies@sentry/profiling-node (recommended for server profiling)Frontend (Vue/React):
@sentry/vue or @sentry/react in package.json dependencies@sentry/vite-plugin for source mapsNode.js Backend:
@sentry/node in package.json dependencies@sentry/profiling-node (recommended)Python:
sentry-sdk in pyproject.toml or requirements.txtRead the Sentry initialization files and check against the compliance tables in REFERENCE.md. Validate:
Additional checks for Next.js projects:
src/instrumentation.ts exists with register() and onRequestError exportssrc/instrumentation-client.ts exists with client-side Sentry initsentry.server.config.ts and sentry.edge.config.ts exist at project rootnext.config.mjs wraps config with withSentryConfig()tunnelRoute: "/monitoring")hideSourceMaps, deleteSourcemapsAfterUpload)@sentry/profiling-node listed in serverExternalPackagessrc/app/error.tsx, src/app/global-error.tsx)enableLogs: true)beforeSendbeforeSendTransaction (drop health checks, static assets)Print a compliance report with:
If --check-only, stop here.
@sentry/vite-plugin for source mapsVerify Sentry integration in CI/CD:
SENTRY_AUTH_TOKEN secret configuredIf missing, offer to add the recommended workflow steps from REFERENCE.md.
Update or create .project-standards.yaml:
standards_version: "2025.1"
project_type: "<detected>"
last_configured: "<timestamp>"
components:
sentry: "2025.1"
| Variable | Description | Required |
|---|---|---|
SENTRY_DSN | Sentry Data Source Name (server-side) | Yes |
NEXT_PUBLIC_SENTRY_DSN | Sentry DSN for client-side (Next.js) | Next.js only |
SENTRY_ENVIRONMENT | Environment name (server-side) | Recommended |
NEXT_PUBLIC_SENTRY_ENVIRONMENT | Environment name (client-side, Next.js) | Next.js only |
SENTRY_ORG | Sentry organization slug | For source maps |
SENTRY_PROJECT | Sentry project slug | For source maps |
SENTRY_AUTH_TOKEN | Auth token for CI/CD | For source maps |
NEXT_PUBLIC_SENTRY_SKIP_BUILD | Skip Sentry webpack plugin in builds | Container builds |
Never commit DSN or auth tokens. Use environment variables or secrets management.
For detailed configuration check tables, initialization templates, and CI/CD workflow examples, see REFERENCE.md.
| Context | Command |
|---|---|
| Quick compliance check | /configure:sentry --check-only |
| Auto-fix all issues | /configure:sentry --fix |
| Frontend project only | /configure:sentry --type frontend |
| Next.js project | /configure:sentry --type nextjs |
| Python project only | /configure:sentry --type python |
| Node.js project only | /configure:sentry --type node |
| Check for hardcoded DSNs | rg -l 'https://[a-f0-9]*@.*sentry\.io' --type-not env |
/configure:instrumentation - Whole observability stack (OTel traces/metrics, structured logging); delegates Sentry gaps to this skill/configure:all - Run all compliance checks/configure:status - Quick compliance overview/configure:workflows - GitHub Actions integrationtypescript-plugin:typescript-sentry - Day-to-day Sentry SDK usage for Bun/Node.js/Next.js (spans, breadcrumbs, cron monitoring, replay)sentry MCP server - Sentry API access for project verificationInstall, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.