sentry-nextjs-sdk

Q: How do I install sentry-nextjs-sdk?

Run npx skills add https://github.com/getsentry/sentry-agent-skills --skill sentry-nextjs-sdk in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sentry-nextjs-sdk/ (personal) or .claude/skills/sentry-nextjs-sdk/ (project).

Q: Which AI agents can use sentry-nextjs-sdk?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Q: Is sentry-nextjs-sdk safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Q: Who maintains sentry-nextjs-sdk?

It is published by getsentry in getsentry/sentry-agent-skills, and it is an official skill from the maker of the technology it covers. It has 653 recorded installs.

by getsentry OfficialDevOps & Cloud

Full Sentry SDK setup for Next.js. Use when asked to "add Sentry to Next.js", "install @sentry/nextjs", or configure error monitoring, tracing, session replay, logging, profiling, AI monitoring, or crons for Next.js applications. Supports Next.js 13+ with App Router and Pages Router.

Installs: 653
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/getsentry/sentry-agent-skills --skill sentry-nextjs-sdk

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads sentry-nextjs-sdk automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Sentry Next.js SDK

Opinionated wizard that scans your Next.js project and guides you through complete Sentry setup across all three runtimes: browser, Node.js server, and Edge.

Invoke This Skill When

User asks to "add Sentry to Next.js" or "set up Sentry" in a Next.js app
User wants to install or configure @sentry/nextjs
User wants error monitoring, tracing, session replay, logging, or profiling for Next.js
User asks about instrumentation.ts, withSentryConfig(), or global-error.tsx
User wants to capture server actions, server component errors, or edge runtime errors

Note: SDK versions and APIs below reflect current Sentry docs at time of writing (@sentry/nextjs ≥8.28.0). Always verify against docs.sentry.io/platforms/javascript/guides/nextjs/ before implementing.

Phase 1: Detect

Run these commands to understand the project before making any recommendations:

# Detect Next.js version and existing Sentry
cat package.json | grep -E '"next"|"@sentry/'

# Detect router type (App Router vs Pages Router)
ls src/app app src/pages pages 2>/dev/null

# Check for existing Sentry config files
ls instrumentation.ts instrumentation-client.ts sentry.server.config.ts sentry.edge.config.ts 2>/dev/null
ls src/instrumentation.ts src/instrumentation-client.ts 2>/dev/null

# Check next.config
ls next.config.ts next.config.js next.config.mjs 2>/dev/null

# Check for existing error boundaries
find . -name "global-error.tsx" -o -name "_error.tsx" 2>/dev/null | grep -v node_modules

# Check build tool
cat package.json | grep -E '"turbopack"|"webpack"'

# Check for logging libraries
cat package.json | grep -E '"pino"|"winston"|"bunyan"'

# Check for companion backend
ls ../backend ../server ../api 2>/dev/null
cat ../go.mod ../requirements.txt ../Gemfile 2>/dev/null | head -3

What to determine:

Question	Impact
Next.js version?	13+ required; 15+ needed for Turbopack support
App Router or Pages Router?	Determines error boundary files needed (`global-error.tsx` vs `_error.tsx`)
`@sentry/nextjs` already present?	Skip install, go to feature config
Existing `instrumentation.ts`?	Merge Sentry into it rather than replace
Turbopack in use?	Tree-shaking in `withSentryConfig` is webpack-only
Logging library detected?	Recommend Sentry Logs integration
Backend directory found?	Trigger Phase 4 cross-link suggestion

Phase 2: Recommend

Present a concrete recommendation based on what you found. Don't ask open-ended questions — lead with a proposal:

Recommended (core coverage):

✅ Error Monitoring — always; captures server errors, client errors, server actions, and unhandled promise rejections
✅ Tracing — server-side request tracing + client-side navigation spans across all runtimes
✅ Session Replay — recommended for user-facing apps; records sessions around errors

Optional (enhanced observability):

⚡ Logging — structured logs via Sentry.logger.*; recommend when pino/winston or log search is needed
⚡ Profiling — continuous profiling; requires Document-Policy: js-profiling header
⚡ AI Monitoring — OpenAI, Vercel AI SDK, Anthropic; recommend when AI/LLM calls detected
⚡ Crons — detect missed/failed scheduled jobs; recommend when cron patterns detected
⚡ Metrics — custom metrics via Sentry.metrics.*; recommend when custom KPIs or business metrics needed

Recommendation logic:

Feature	Recommend when...
Error Monitoring	Always — non-negotiable baseline
Tracing	Always for Next.js — server route tracing + client navigation are high-value
Session Replay	User-facing app, login flows, or checkout pages
Logging	App uses structured logging or needs log-to-trace correlation
Profiling	Performance-critical app; client sets `Document-Policy: js-profiling`
AI Monitoring	App makes OpenAI, Vercel AI SDK, or Anthropic calls
Crons	App has Vercel Cron jobs, scheduled API routes, or `node-cron` usage
Metrics	App needs custom counters, gauges, or histograms via `Sentry.metrics.*`

Propose: "I recommend setting up Error Monitoring + Tracing + Session Replay. Want me to also add Logging or Profiling?"

Phase 3: Guide

Option 1: Wizard (Recommended)

npx @sentry/wizard@latest -i nextjs

The wizard walks you through login, org/project selection, and auth token setup interactively — no manual token creation needed. It then installs the SDK, creates all necessary config files (instrumentation-client.ts, sentry.server.config.ts, sentry.edge.config.ts, instrumentation.ts), wraps next.config.ts with withSentryConfig(), configures source map upload, and adds a /sentry-example-page for verification.

Skip to Verification after running the wizard.

Option 2: Manual Setup

Install

npm install @sentry/nextjs --save

Create `instrumentation-client.ts` — Browser / Client Runtime

Older docs used sentry.client.config.ts — the current pattern is instrumentation-client.ts.

import * as Sentry from "@sentry/nextjs";

Sentry.init({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN ?? "___PUBLIC_DSN___",

  sendDefaultPii: true,

  // 100% in dev, 10% in production
  tracesSampleRate: process.env.NODE_ENV === "development" ? 1.0 : 0.1,

  // Session Replay: 10% of all sessions, 100% of sessions with errors
  replaysSessionSampleRate: 0.1,
  replaysOnErrorSampleRate: 1.0,

  enableLogs: true,

  integrations: [
    Sentry.replayIntegration(),
    // Optional: user feedback widget
    // Sentry.feedbackIntegration({ colorScheme: "system" }),
  ],
});

// Hook into App Router navigation transitions (App Router only)
export const onRouterTransitionStart = Sentry.captureRouterTransitionStart;

Create `sentry.server.config.ts` — Node.js Server Runtime

import * as Sentry from "@sentry/nextjs";

Sentry.init({
  dsn: process.env.SENTRY_DSN ?? "___DSN___",

  sendDefaultPii: true,
  tracesSampleRate: process.env.NODE_ENV === "development" ? 1.0 : 0.1,

  // Attach local variable values to stack frames
  includeLocalVariables: true,

  enableLogs: true,
});

Create `sentry.edge.config.ts` — Edge Runtime

import * as Sentry from "@sentry/nextjs";

Sentry.init({
  dsn: process.env.SENTRY_DSN ?? "___DSN___",

  sendDefaultPii: true,
  tracesSampleRate: process.env.NODE_ENV === "development" ? 1.0 : 0.1,

  enableLogs: true,
});

Create `instrumentation.ts` — Server-Side Registration Hook

Requires experimental.instrumentationHook: true in next.config for Next.js < 14.0.4. It's stable in 14.0.4+.

import * as Sentry from "@sentry/nextjs";

export async function register() {
  if (process.env.NEXT_RUNTIME === "nodejs") {
    await import("./sentry.server.config");
  }

  if (process.env.NEXT_RUNTIME === "edge") {
    await import("./sentry.edge.config");
  }
}

// Automatically captures all unhandled server-side request errors
// Requires @sentry/nextjs >= 8.28.0
export const onRequestError = Sentry.captureRequestError;

Runtime dispatch:

`NEXT_RUNTIME`	Config file loaded
`"nodejs"`	`sentry.server.config.ts`
`"edge"`	`sentry.edge.config.ts`
(client bundle)	`instrumentation-client.ts` (Next.js handles this directly)

App Router: Create `app/global-error.tsx`

This catches errors in the root layout and React render errors:

"use client";

import * as Sentry from "@sentry/nextjs";
import NextError from "next/error";
import { useEffect } from "react";

export default function GlobalError({
  error,
}: {
  error: Error & { digest?: string };
}) {
  useEffect(() => {
    Sentry.captureException(error);
  }, [error]);

  return (
    <html>
      <body>
        <NextError statusCode={0} />
      </body>
    </html>
  );
}

Pages Router: Update `pages/_error.tsx`

import * as Sentry from "@sentry/nextjs";
import type { NextPageContext } from "next";
import NextErrorComponent from "next/error";

type ErrorProps = { statusCode: number };

export default function CustomError({ statusCode }: ErrorProps) {
  return <NextErrorComponent statusCode={statusCode} />;
}

CustomError.getInitialProps = async (ctx: NextPageContext) => {
  await Sentry.captureUnderscoreErrorException(ctx);
  return NextErrorComponent.getInitialProps(ctx);
};

Wrap `next.config.ts` with `withSentryConfig()`

import type { NextConfig } from "next";
import { withSentryConfig } from "@sentry/nextjs";

const nextConfig: NextConfig = {
  // your existing Next.js config
};

export default withSentryConfig(nextConfig, {
  org: "___ORG_SLUG___",
  project: "___PROJECT_SLUG___",

  // Source map upload auth token (see Source Maps section below)
  authToken: process.env.SENTRY_AUTH_TOKEN,

  // Upload wider set of client source files for better stack trace resolution
  widenClientFileUpload: true,

  // Create a proxy API route to bypass ad-blockers
  tunnelRoute: "/monitoring",

  // Suppress non-CI output
  silent: !process.env.CI,
});

Exclude Tunnel Route from Middleware

If you have middleware.ts, exclude the tunnel path from auth or redirect logic:

// middleware.ts
export const config = {
  matcher: [
    // Exclude monitoring route, Next.js internals, and static files
    "/((?!monitoring|_next/static|_next/image|favicon.ico).*)",
  ],
};

Source Maps Setup

Source maps make production stack traces readable — without them, you see minified code. This is non-negotiable for production apps.

Step 1: Generate a Sentry auth token

Go to sentry.io/settings/auth-tokens/ and create a token with project:releases and org:read scopes.

Step 2: Set environment variables

# .env.sentry-build-plugin  (gitignore this file)
SENTRY_AUTH_TOKEN=sntrys_eyJ...

Or set in CI secrets:

SENTRY_AUTH_TOKEN=sntrys_eyJ...
SENTRY_ORG=my-org        # optional if set in next.config
SENTRY_PROJECT=my-project # optional if set in next.config

Step 3: Add to .gitignore

.env.sentry-build-plugin

Step 4: Verify authToken is wired in next.config.ts

withSentryConfig(nextConfig, {
  org: "my-org",
  project: "my-project",
  authToken: process.env.SENTRY_AUTH_TOKEN, // reads from .env.sentry-build-plugin or CI env
  widenClientFileUpload: true,
});

Source maps are uploaded automatically on every next build.

For Each Agreed Feature

Load the corresponding reference file and follow its steps:

Feature	Reference file	Load when...
Error Monitoring	`references/error-monitoring.md`	Always (baseline) — App Router error boundaries, Pages Router `_error.tsx`, server action wrapping
Tracing	`references/tracing.md`	Server-side request tracing, client navigation, distributed tracing, `tracePropagationTargets`
Session Replay	`references/session-replay.md`	User-facing app; privacy masking, canvas recording, network capture
Logging	`references/logging.md`	Structured logs, `Sentry.logger.*`, log-to-trace correlation
Profiling	`references/profiling.md`	Continuous profiling, `Document-Policy` header, `nodeProfilingIntegration`
AI Monitoring	`references/ai-monitoring.md`	App uses OpenAI, Vercel AI SDK, or Anthropic
Crons	`references/crons.md`	Vercel Cron, scheduled API routes, `node-cron`

For each feature: read the reference file, follow its steps exactly, and verify before moving on.

Verification

After wizard or manual setup, verify Sentry is working:

// Add temporarily to a server action or API route, then remove
import * as Sentry from "@sentry/nextjs";

throw new Error("Sentry test error — delete me");
// or
Sentry.captureException(new Error("Sentry test error — delete me"));

Then check your Sentry Issues dashboard — the error should appear within ~30 seconds.

Verification checklist:

Check	How
Client errors captured	Throw in a client component, verify in Sentry
Server errors captured	Throw in a server action or API route
Edge errors captured	Throw in middleware or edge route handler
Source maps working	Check stack trace shows readable file names
Session Replay working	Check Replays tab in Sentry dashboard

Config Reference

`Sentry.init()` Options

Option	Type	Default	Notes
`dsn`	`string`	—	Required. Use `NEXT_PUBLIC_SENTRY_DSN` for client, `SENTRY_DSN` for server
`tracesSampleRate`	`number`	—	0–1; 1.0 in dev, 0.1 in prod recommended
`replaysSessionSampleRate`	`number`	`0.1`	Fraction of all sessions recorded
`replaysOnErrorSampleRate`	`number`	`1.0`	Fraction of error sessions recorded
`sendDefaultPii`	`boolean`	`false`	Include IP, request headers in events
`includeLocalVariables`	`boolean`	`false`	Attach local variable values to stack frames (server only)
`enableLogs`	`boolean`	`false`	Enable Sentry Logs product
`environment`	`string`	auto	`"production"`, `"staging"`, etc.
`release`	`string`	auto	Set to commit SHA or version tag
`debug`	`boolean`	`false`	Log SDK activity to console

`withSentryConfig()` Options

Option	Type	Notes
`org`	`string`	Sentry organization slug
`project`	`string`	Sentry project slug
`authToken`	`string`	Source map upload token (`SENTRY_AUTH_TOKEN`)
`widenClientFileUpload`	`boolean`	Upload more client files for better stack traces
`tunnelRoute`	`string`	API route path for ad-blocker bypass (e.g. `"/monitoring"`)
`silent`	`boolean`	Suppress build output (`!process.env.CI` recommended)
`webpack.treeshake.*`	`object`	Tree-shake SDK features (webpack only, not Turbopack)

Environment Variables

Variable	Runtime	Purpose
`NEXT_PUBLIC_SENTRY_DSN`	Client	DSN for browser Sentry init (public)
`SENTRY_DSN`	Server / Edge	DSN for server/edge Sentry init
`SENTRY_AUTH_TOKEN`	Build	Source map upload auth token (secret)
`SENTRY_ORG`	Build	Org slug (alternative to `org` in config)
`SENTRY_PROJECT`	Build	Project slug (alternative to `project` in config)
`SENTRY_RELEASE`	Server	Release version string (auto-detected from git)
`NEXT_RUNTIME`	Server / Edge	`"nodejs"` or `"edge"` (set by Next.js internally)

Phase 4: Cross-Link

After completing Next.js setup, check for companion services:

# Check for backend services in adjacent directories
ls ../backend ../server ../api ../services 2>/dev/null

# Check for backend language indicators
cat ../go.mod 2>/dev/null | head -3
cat ../requirements.txt ../pyproject.toml 2>/dev/null | head -3
cat ../Gemfile 2>/dev/null | head -3
cat ../pom.xml ../build.gradle 2>/dev/null | head -3

If a backend is found, suggest the matching SDK skill:

Backend detected	Suggest skill
Go (`go.mod`)	`sentry-go-sdk`
Python (`requirements.txt`, `pyproject.toml`)	`sentry-python-sdk`
Ruby (`Gemfile`)	`sentry-ruby-sdk`
Java/Kotlin (`pom.xml`, `build.gradle`)	See docs.sentry.io/platforms/java/
Node.js (Express, Fastify, Hapi)	`@sentry/node` — see docs.sentry.io/platforms/javascript/guides/express/

Connecting frontend and backend with the same DSN or linked projects enables distributed tracing — stack traces that span your browser, Next.js server, and backend API in a single trace view.

Troubleshooting

Issue	Cause	Solution
Events not appearing	DSN misconfigured or `debug: false` hiding errors	Set `debug: true` temporarily; check browser network tab for requests to `sentry.io`
Stack traces show minified code	Source maps not uploading	Check `SENTRY_AUTH_TOKEN` is set; run `next build` and look for "Source Maps" in build output
`onRequestError` not firing	SDK version < 8.28.0	Upgrade: `npm install @sentry/nextjs@latest`
Edge runtime errors missing	`sentry.edge.config.ts` not loaded	Verify `instrumentation.ts` imports it when `NEXT_RUNTIME === "edge"`
Tunnel route returns 404	`tunnelRoute` set but Next.js route missing	The plugin creates it automatically; check you ran `next build` after adding `tunnelRoute`
`withSentryConfig` tree-shaking breaks build	Turbopack in use	Tree-shaking options only work with webpack; remove `webpack.treeshake` options when using Turbopack
`global-error.tsx` not catching errors	Missing `"use client"` directive	Add `"use client"` as the very first line of `global-error.tsx`
Session Replay not recording	`replayIntegration()` missing from client init	Add `Sentry.replayIntegration()` to `integrations` in `instrumentation-client.ts`

FAQ

What does the sentry-nextjs-sdk skill do?

How do I install sentry-nextjs-sdk?

Run npx skills add https://github.com/getsentry/sentry-agent-skills --skill sentry-nextjs-sdk in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sentry-nextjs-sdk/ (personal) or .claude/skills/sentry-nextjs-sdk/ (project).

Which AI agents can use sentry-nextjs-sdk?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is sentry-nextjs-sdk safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains sentry-nextjs-sdk?

It is published by getsentry in getsentry/sentry-agent-skills, and it is an official skill from the maker of the technology it covers. It has 653 recorded installs.

More from getsentry/sentry-agent-skills

View all →

sentry-fix-issues

getsentry/sentry-agent-skills

Find and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry. Methodically analyzes stack traces, breadcrumbs, traces, and context to identify root causes.

OfficialDevOps & Cloud2.6K installs

sentry-react-setup

getsentry/sentry-agent-skills

Setup Sentry in React apps. Use when asked to add Sentry to React, install @sentry/react, or configure error monitoring, error boundaries, session replay, or browser tracing for React applications.

OfficialDevOps & Cloud1.1K installs

sentry-setup-ai-monitoring

getsentry/sentry-agent-skills

Setup Sentry AI Agent Monitoring in any project. Use when asked to monitor LLM calls, track AI agents, or instrument OpenAI/Anthropic/Vercel AI/LangChain/Google GenAI/Pydantic AI. Detects installed AI SDKs and configures appropriate integrations.

OfficialDevOps & Cloud894 installs

sentry-pr-code-review

getsentry/sentry-agent-skills

Review a project's PRs to check for issues detected in code review by Seer Bug Prediction. Use when asked to review or fix issues identified by Sentry in PR comments, or to find recent PRs with Sentry feedback.

OfficialCode Quality & Workflow632 installs

sentry-create-alert

getsentry/sentry-agent-skills

Create Sentry alerts using the workflow engine API. Use when asked to create alerts, set up notifications, configure issue priority alerts, or build workflow automations. Supports email, Slack, PagerDuty, Discord, and other notification actions.

OfficialDevOps & Cloud592 installs

sentry-react-sdk

getsentry/sentry-agent-skills

Full Sentry SDK setup for React. Use when asked to "add Sentry to React", "install @sentry/react", or configure error monitoring, tracing, session replay, profiling, or logging for React applications. Supports React 16+, React Router v5-v7, TanStack Router, Redux, Vite, and webpack.

OfficialDevOps & Cloud580 installs

Popular devops & cloud skills

View category →

microsoft-foundry

microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure

OfficialDevOps & Cloud579.1K installs

azure-diagnostics

microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

OfficialDevOps & Cloud569.8K installs

azure-prepare

microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

OfficialDevOps & Cloud569K installs

azure-ai

microsoft/azure-skills

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.

OfficialDevOps & Cloud568.8K installs

azure-deploy

microsoft/azure-skills

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

OfficialDevOps & Cloud568.6K installs

azure-validate

microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.

OfficialDevOps & Cloud568K installs

sentry-nextjs-sdk

Install

Install

Describe the task

Review the result

SKILL.md

Sentry Next.js SDK

Invoke This Skill When

Phase 1: Detect

Phase 2: Recommend

Phase 3: Guide

Option 1: Wizard (Recommended)

Option 2: Manual Setup

Install

Create instrumentation-client.ts — Browser / Client Runtime

Create sentry.server.config.ts — Node.js Server Runtime

Create sentry.edge.config.ts — Edge Runtime

Create instrumentation.ts — Server-Side Registration Hook

App Router: Create app/global-error.tsx

Pages Router: Update pages/_error.tsx

Wrap next.config.ts with withSentryConfig()

Exclude Tunnel Route from Middleware

Source Maps Setup

For Each Agreed Feature

Verification

Config Reference

Sentry.init() Options

withSentryConfig() Options

Environment Variables

Phase 4: Cross-Link

Troubleshooting

FAQ

More from getsentry/sentry-agent-skills

Popular devops & cloud skills

Create `instrumentation-client.ts` — Browser / Client Runtime

Create `sentry.server.config.ts` — Node.js Server Runtime

Create `sentry.edge.config.ts` — Edge Runtime

Create `instrumentation.ts` — Server-Side Registration Hook

App Router: Create `app/global-error.tsx`

Pages Router: Update `pages/_error.tsx`

Wrap `next.config.ts` with `withSentryConfig()`

`Sentry.init()` Options

`withSentryConfig()` Options