This repository is the single source of truth for skills and routing metadata,
but it is not itself an installable plugin, and each assistant (Claude Code,
Cursor, Codex, Grok) expects the plugin in a different on-disk shape. No plugin
ecosystem can consume a zip or release asset; all install from a git ref. So a
GitHub Actions workflow builds each agent's distribution from this repository
and deploys it to a dedicated repository whose root is exactly that agent's
plugin, which a marketplace points at as getsentry/plugin-<agent>.
Each agent has a `plugin-src/<agent>/` dir with its manifests, README, and a
`build.sh` that assembles the dist tree from shared repo content. Claude, Cursor,
and Grok consume the plugin at the repo root; Codex requires it under
`plugins/sentry/` and rejects the `disable-model-invocation` field the skill
tree relies on, so its build strips that field and emits a per-skill
`agents/openai.yaml` (see `hide-skills.py`). MCP config is built from the repo's
`mcp.json` source of truth: inline in Claude's manifest, and a file for the
others.
Cross-repo writes use a short-lived token from a dedicated GitHub App scoped to
contents:write on the plugin repos; the default GITHUB_TOKEN cannot push to
other repositories.
The root `.claude-plugin/`, `.cursor-plugin/`, and `.mcp.json` are retained so
existing installs that consumed the plugin from this repo's root keep working;
their READMEs announce removal on or after 2026-07-11.
* feat(instrumentation-guide): add sentry-instrumentation-guide skill
A decision-framework skill that helps an agent (or developer) choose which
Sentry signal to reach for when instrumenting code — error, span, span
attribute, log, or metric — and why the choice decides what's debuggable later.
Distilled from the "Errors, Traces, Logs, Metrics: When to Reach for What" post.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* feat(instrumentation-guide): add reference deep-dives
choosing-signals.md: per-signal detail, the four overlap tiebreakers, the
sampling-vs-filtering rationale, and the "wide events" argument.
instrumentation-examples.md: one handler instrumented end to end in Python and
JS/TS, showing span attribute vs log vs metric on the same decision.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* docs(skills): register sentry-instrumentation-guide
Add to the sentry-feature-setup router (decision bullet + table row), the
AGENTS.md and README feature tables, and regenerate SKILL_TREE.md.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* refactor(instrumentation-guide): defer signatures to sibling SDK skills
This skill decides WHAT signal to emit; the sentry-*-sdk skills own HOW
(setup, API signatures, enabling flags, min versions) in their
references/{tracing,logging,metrics}.md. Stop hardcoding docs.sentry.io
deep links and a Node-specific link in the language-neutral examples/
sampling sections — point at the matching SDK skill by name instead, so
there's one maintained source of truth and nothing to go stale.
Kept: top-level product-area links (one per signal) for orientation.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* instrumentation-guide: align signal naming with the blog post
- Four-signals table and deep dive lead with Traces (spans named as the unit)
- Gut-check "reach for" column shows Traces / Spans
- Metrics question -> "How's this trending over time?"
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* feat(php-sdk): add sentry-php-sdk main SKILL.md wizard
Add the primary wizard skill for PHP SDK setup covering plain PHP, Laravel, and
Symfony in a single skill following the one-skill-per-language pattern used by
Python, Ruby, and .NET skills.
The wizard follows the standard 4-phase structure:
- Phase 1 (Detect): composer.json inspection, filesystem markers (artisan /
bin/console), framework and queue detection
- Phase 2 (Recommend): concrete proposal matrix for Error Monitoring, Tracing,
Profiling, Logging, Metrics, and Crons
- Phase 3 (Guide): framework-branched installation and initialization — plain
PHP uses \Sentry\init(), Laravel uses artisan sentry:publish + Integration::handles(),
Symfony uses YAML bundle config
- Phase 4 (Cross-Link): detects companion frontend (React, Svelte, Vue) and
suggests the matching frontend SDK skill
Key design decisions:
- No wizard CLI (php/laravel/symfony not supported by @sentry/wizard)
- Laravel artisan sentry:publish --dsn= documented as the closest equivalent
- Profiling clearly marked as requiring the excimer PECL extension (Linux/macOS only)
- Metrics marked as beta using the TraceMetrics API
- Framework-specific deep dives deferred to references/laravel.md and references/symfony.md
Creates the references/ directory (populated in subsequent commits).
Co-Authored-By: Claude Sonnet 4.5 (Anthropic)
* feat(php-sdk): add profiling, logging, metrics, and crons reference files
Add four reference files to skills/sentry-php-sdk/references/ covering the
full set of PHP SDK observability features:
- profiling.md: Excimer extension prerequisites, version requirements per
framework (PHP ≥3.15, Laravel ≥3.3, Symfony ≥4.7), profiles_sample_rate
semantics (relative to traces_sample_rate), FastCGI latency mitigation,
and Relay proxy setup
- logging.md: Structured Sentry Logs feature (enable_logs: true), direct
logger API (\Sentry\logger()), Monolog bridge, Laravel sentry_logs channel
setup via .env and config/logging.php, Symfony LogsHandler + monolog.yaml
wiring, before_send_log filtering (closure for PHP/Laravel, service ID for
Symfony), auto-added attributes table, flush semantics per runtime context
- metrics.md: TraceMetrics API (count/distribution/gauge), deprecation notice
for old \Sentry\metrics() API, unit enum reference, ring buffer flush
behavior (cap 1000), before_send_metric filtering, auto-added attributes,
Symfony YAML configuration
- crons.md: withMonitor() wrapper, manual captureCheckIn() pattern, heartbeat
pattern, programmatic MonitorConfig upsert (crontab + interval schedules),
Laravel sentryMonitor() macro with full parameter reference, Symfony direct
SDK usage (no framework-specific integration), CheckInStatus/MonitorSchedule
references, rate limits (6/min per monitor-environment), alerts setup
All files follow the structure established by the sentry-python-sdk references.
Co-Authored-By: Claude Sonnet 4.6 (Anthropic)
* feat(php-sdk): add Laravel and Symfony framework reference deep-dives
Adds two comprehensive framework-specific reference files for the sentry-php-sdk skill:
- references/laravel.md (~496 lines): Full deep dive covering installation (Laravel 11+ vs 10 exception handler patterns), all config/sentry.php options including breadcrumb and tracing sub-arrays with ENV variable names, auto-instrumented operations table (11+ operations), filesystem disk opt-in instrumentation, auto-registered middleware, both log channel drivers (sentry vs sentry_logs), full queue distributed tracing with payload keys, sentryMonitor() macro with all parameters, Artisan commands, closures-and-config-cache gotcha with static callable workaround, Lumen support, Laravel Octane scope isolation warning, and Pennant feature flags integration.
- references/symfony.md (~531 lines): Full deep dive covering Flex auto-registration vs manual bundle setup, complete sentry.yaml schema with all top-level/options/messenger/tracing sub-nodes, Symfony-specific defaults (kernel.environment, PrettyVersions release, in_app_exclude auto-includes), bundle-level options table, DIC callable pattern with full service factory example (critical Symfony gotcha — YAML can't hold closures), auto-instrumented operations table (Doctrine DBAL, Twig, Cache, HTTP Client), structured logs via LogsHandler Monolog service, traditional Monolog handler with buffer support, Messenger integration (error-capture only, no tracing spans), cron monitoring using base PHP SDK functions, console command tracing config, all auto-registered event listeners, and automatic distributed tracing header handling.
These are loaded conditionally by the main SKILL.md when Laravel or Symfony is detected in the project's composer.json.
Co-Authored-By: Claude claude.ai/code
* docs(sentry-php-sdk): add error monitoring and tracing reference files
Add two comprehensive reference documents for the PHP SDK skill:
- references/error-monitoring.md — covers all capture APIs (captureException,
captureMessage, captureEvent, captureLastError), Hub/Scope management
(configureScope, withScope, withContext, push/pop), context enrichment (tags,
UserDataBag, Breadcrumb TYPE_* and LEVEL_* constants, setContext), before_send
and before_breadcrumb hooks with exact callback signatures, EventHint and
ExceptionMechanism for handled/unhandled distinction, exception chaining,
fingerprinting via Scope and before_send, and framework-specific integration
notes for plain PHP, Laravel, and Symfony. Includes a 5-row troubleshooting
table.
- references/tracing.md — covers traces_sample_rate / traces_sampler config
(including Symfony service-factory pattern for closures), the full custom
span API (TransactionContext, SpanContext, startChild, Sentry\trace() helper,
safe manual pattern), auto-instrumentation matrix for Laravel (15+ operations)
and Symfony (12+ operations), distributed tracing with sentry-trace + baggage
headers (Guzzle middleware, continueTrace(), queue worker pattern), HTML meta
tag injection for frontend/backend stitching, profiling with Excimer extension,
a span ops cheat-sheet table, and an 8-row troubleshooting table.
Both files mirror the structure of the sentry-python-sdk reference files
(config table → code examples → best practices / framework notes → troubleshooting).
Co-Authored-By: claude-sonnet-4-5 <claude-sonnet-4-5@anthropic.com>
* docs(php-sdk): register sentry-php-sdk in router, skill tree, and README
Add sentry-php-sdk to all skill registry locations:
- sentry-sdk-setup/SKILL.md: add PHP row to routing table and detection
instruction for composer.json with laravel/framework or symfony/framework-bundle
- SKILL_TREE.md: regenerated via build-skill-tree.sh with PHP entry
- AGENTS.md: add sentry-php-sdk to SDK Skills table
- README.md: add PHP (Laravel, Symfony) to SDK skills listing
- Remove stale .gitkeep from references/ (replaced by actual reference files)
Co-Authored-By: Claude Sonnet 4.5 (Anthropic)
* fix(php-sdk): address review findings — remove fabricated APIs, fix routing
Three P1 bugs and five P2 issues resolved:
P1 — Router step numbering: The PHP detection rule was numbered 6 but
appeared before the fallback step 5, creating sequence 1,2,3,4,6,5.
Corrected to 1,2,3,4,5,6 so LLMs process rules in the right priority order.
P1 — Fabricated \Sentry\withContext() API: This function does not exist
in sentry-php 4.x. Removed from the scope API table, code example, plain
PHP notes, and Octane troubleshooting row. Replaced with the correct
pushScope()/popScope() pattern throughout error-monitoring.md.
P1 — continueTrace() return value discarded: The 'Extracting incoming
trace context' example called continueTrace() without capturing its
TransactionContext return value, then created a fresh context — meaning
the transaction would never be linked to the upstream trace. Fixed to
assign the return value and use it directly, matching the correct pattern
already shown in the queue consumer example.
P2 — error_types default inconsistent: error-monitoring.md said E_ALL;
SKILL.md and the SDK research both say null/error_reporting(). Updated
the reference to error_reporting() for consistency with the SDK source.
P2 — Phantom 'never' value for max_request_body_size: Removed the
undocumented 'never' option. Valid values are none/small/medium/always.
P2 — Package name sentry/sentry-php vs sentry/sentry: All reference file
headers used sentry/sentry-php (the GitHub repo name) instead of
sentry/sentry (the Packagist package). Fixed across crons.md,
error-monitoring.md, logging.md, metrics.md, profiling.md, and tracing.md.
P2 — Tracing header mixed profiling version noise: Simplified the
tracing.md header to just SDK minimums; profiling version details already
live in profiling.md where they belong.
Co-Authored-By: Claude Sonnet 4.5 (Anthropic)
* chore: remove review artifacts from tracked files
---------
Co-authored-by: claude-sonnet-4-5 <claude-sonnet-4-5@anthropic.com>
* feat(node-sdk): add sentry-node-sdk main SKILL.md wizard
Introduces the sentry-node-sdk skill covering all three JS server-side
runtimes in a single unified wizard: Node.js, Bun, and Deno.
Key design decisions:
- One skill for all three runtimes — Bun is a thin wrapper over @sentry/node
(shares 99% of the API), and Deno shares the same core Sentry primitives,
so a unified skill with runtime-specific sections is cleaner than three
separate skills.
- Node.js wizard path: 'npx @sentry/wizard@latest -i node' is offered as
the recommended first option; manual setup covers CJS (require + first
line) and ESM (--import ./instrument.mjs flag, Node 18.19.0+ required).
- Bun: 'bun --preload ./instrument.ts' pattern; profiling explicitly marked
as unsupported (native addon incompatible).
- Deno: npm: specifier only (deno.land/x/sentry is deprecated); Deno 2.0+
required; --allow-net permissions documented; denoCronIntegration noted.
- All six framework error handlers documented (Express, Fastify, Koa, Hapi,
Connect, NestJS) with placement rules and async flag for Hapi.
- Feature support matrix per runtime so agents don't suggest profiling on Bun/Deno.
- Four-phase structure (Detect → Recommend → Guide → Cross-Link) consistent
with every other SDK skill in the bundle.
Also:
- Registers sentry-node-sdk in the sentry-sdk-setup router table
- Updates routing instructions (Next.js preference over node-sdk)
- Regenerates SKILL_TREE.md via build-skill-tree.sh (0 errors)
Co-Authored-By: Claude Sonnet 4.5 (Anthropic AI assistant)
* feat(node-sdk): add error monitoring reference for sentry-node-sdk
Adds a comprehensive ~1200-line error monitoring reference covering:
- Instrument-first rule with CJS and ESM startup patterns
- Auto-captured vs manual errors — the 'swallowed catch' gotcha
- Framework error handler placement rules (critical: differs per framework)
- Express: setupExpressErrorHandler AFTER routes
- Fastify: setupFastifyErrorHandler BEFORE routes
- Koa: setupKoaErrorHandler as FIRST middleware
- Hapi: await setupHapiErrorHandler (async — must await!)
- Connect: setupConnectErrorHandler BEFORE routes
- NestJS: SentryGlobalFilter + SentryModule.forRoot()
- Full captureException/captureMessage API with TypeScript signatures
- Scope management (v8+ Hub removal): global, isolation, current scopes
- withScope vs withIsolationScope — when to use each
- Context enrichment: setTag, setContext, setUser, setExtra, addBreadcrumb
- beforeSend, beforeBreadcrumb, ignoreErrors filtering
- Fingerprinting: per-capture, withScope, beforeSend global rules
- Event processors vs beforeSend (unlimited vs one-only)
- requestDataIntegration PII opt-in (body/cookies/IP)
- Error chains via linkedErrorsIntegration (Error.cause)
- Lifecycle: flush/close before shutdown (critical for serverless)
- Bun runtime: --preload pattern, profiling incompatibility
- Deno runtime: npm: specifier, Deno 2+ requirements
- Quick reference card
Co-Authored-By: Claude Sonnet 4.5 (Anthropic)
* feat(node-sdk): add tracing reference for sentry-node-sdk
Adds a comprehensive 816-line tracing reference covering:
- OTel-native architecture in v8+: SentrySpanProcessor, SentryPropagator,
SentrySampler, SentryContextManager and how they compose
- Full auto-instrumentation table (28+ packages) across HTTP, databases
(pg, mysql2, mongodb, redis, prisma, sequelize, typeorm, knex), message
queues (kafkajs, amqplib, pubsub, SNS/SQS, bull, bullmq), GraphQL, and
AI/LLM libraries (OpenAI, Anthropic, LangChain, Vercel AI, Google GenAI)
- Custom span APIs: startSpan (auto-end), startSpanManual (manual end),
startInactiveSpan (not active), withActiveSpan (temporarily activate)
with real-world usage examples including middleware and parallel ops
- Sampling: tracesSampleRate, tracesSampler with SamplingContext shape,
inheritOrSampleWith() (v9+), and precedence rules
- Distributed tracing: sentry-trace/baggage headers, tracePropagationTargets,
continueTrace(), manual propagation over Kafka/AMQP/WebSocket
- Advanced APIs: startNewTrace(), suppressTracing(), forceTransaction,
onlyIfParent, ignoreSpans, beforeSendSpan, getActiveSpan, getRootSpan
- Framework auto-instrumentation patterns for Express, Fastify, Koa,
Hapi, and NestJS (with @SentryTraced decorator)
- Runtime differences table: Node.js (full), Bun (via Node, no profiling),
Deno (limited auto-instrumentation, manual HTTP wrapping required)
- Troubleshooting table for 12 common issues
Co-Authored-By: Claude claude.ai/code
* docs(sentry-node-sdk): add profiling.md reference
Add comprehensive profiling reference for the sentry-node-sdk skill covering
the @sentry/profiling-node native addon and all its configuration options.
Key points documented:
- Node.js only: native C++ addon via V8 CpuProfiler; Bun and Deno are
explicitly NOT supported (clearly called out at top and in platform table)
- Installation with strict version-matching requirement
- Trace mode (auto-attach to spans) vs manual mode (startProfiler/stopProfiler)
- Continuous profiling for long-running processes and batch jobs
- V2 chunk-based architecture: 60-second upload windows, no 30s cap
- profileSessionSampleRate semantics (once per process startup, not per request)
- Supported platforms table: macOS/Linux/Windows, x64/ARM64, Node 18-24
- Environment variables: SENTRY_PROFILER_BINARY_PATH, SENTRY_PROFILER_LOGGING_MODE
- Production recommendations with performance impact notes
- Alpine/Docker setup (musl libc variant, rebuild steps)
- 10-entry troubleshooting table covering all common failure modes
Follows the pattern established by skills/sentry-nextjs-sdk/references/profiling.md
but scoped to Node.js only (no browser profiling section).
Co-Authored-By: claude-sonnet-4-5 (Anthropic)
* docs(sentry-node-sdk): add logging, metrics, and crons reference files
Three new reference files for the sentry-node-sdk skill:
- logging.md: Covers the GA Sentry.logger.* API (v9.41.0+), the fmt tagged
template literal for parameterized messages, scope-based attributes
(v10.32.0+), consoleLoggingIntegration, createConsolaReporter, the
beforeSendLog hook, manual Winston/Pino bridge patterns (no official
transports), trace linking, buffer flushing, and a troubleshooting table.
- metrics.md: Covers the Open Beta Sentry.metrics.* API (v10.25.0+) with the
three methods count/gauge/distribution (no increment or set in v10), unit
strings, attribute cardinality guidance, scope-based attributes (v10.33.0+),
beforeSendMetric hook, and flush semantics.
- crons.md: Covers the GA crons API (v7.51.1+) including captureCheckIn,
withMonitor, heartbeat vs start/finish patterns, MonitorConfig upsert,
crontab and interval schedule types, official instrumentNodeCron /
instrumentCron / instrumentNodeSchedule helpers, manual patterns for Agenda
and BullMQ, serverless flush requirement, and rate limit details.
Co-Authored-By: Claude Sonnet 4.5 (Anthropic)
* docs: register sentry-node-sdk in AGENTS.md and README.md
Add sentry-node-sdk to the SDK Skills table in both AGENTS.md and README.md.
The skill was already registered in sentry-sdk-setup router and SKILL_TREE.md
from prior work; this completes the documentation surface.
Co-Authored-By: Claude Sonnet 4.6 (Anthropic)
* fix(node-sdk): address review findings — handler placement, NestJS imports, troubleshooting
P0: Fix Fastify error handler placement in SKILL.md (BEFORE routes, not after)
P0: Fix Connect error handler placement in SKILL.md (BEFORE routes, not after)
P1: Remove erroneous await on setupFastifyErrorHandler in tracing.md
P1: Fix SentryGlobalFilter import path to @sentry/nestjs/setup in SKILL.md
P1: Add missing Troubleshooting section to error-monitoring.md (11 entries)
P2: Add Deno denoCronIntegration section to crons.md reference
Co-Authored-By: Claude Sonnet 4 (Anthropic)
* refactor(node-sdk): defer NestJS/Next.js to their dedicated skills
Replace inline NestJS setup code in SKILL.md, error-monitoring.md, and
tracing.md with cross-references to sentry-nestjs-sdk. NestJS uses a
separate package (@sentry/nestjs) with NestJS-native decorators, filters,
and GraphQL support — the dedicated skill covers it better.
Update the SDK router to:
- Add NestJS routing priority (rule 3: prefer sentry-nestjs-sdk)
- Remove NestJS from sentry-node-sdk framework list
- Clarify sentry-node-sdk is the fallback for generic Node/Bun/Deno
Update Phase 4 cross-link table to prominently surface both
sentry-nestjs-sdk and sentry-nextjs-sdk as preferred alternatives
when those frameworks are detected.
Co-Authored-By: Claude Sonnet 4 (Anthropic)
* chore: remove review files
Remove .pi/review.md and review.md that were accidentally included in the PR.
Add sentry-android-sdk to all discovery surfaces so the new skill is
reachable through every entry point:
- skills/sentry-sdk-setup/SKILL.md: add Android row to the routing table
(alphabetically between the implicit position before Cocoa) and a
dedicated routing instruction — 'If Android (build.gradle with android
plugin) is detected, use sentry-android-sdk'
- README.md: add sentry-android-sdk to the SDK Setup Wizards table
- AGENTS.md: add sentry-android-sdk to the SDK Skills table
- SKILL_TREE.md: regenerated via scripts/build-skill-tree.sh — 20 skills
scanned, 3 routers, 0 errors
Co-Authored-By: Claude claude.ai/code
Add the new NestJS SDK skill to both documentation files so it's
discoverable alongside the existing SDK skills. Listed alphabetically
between Go and Next.js with its key framework support noted:
Express, Fastify, GraphQL, Microservices, and WebSocket.
Co-Authored-By: Claude Sonnet 4 (Anthropic)
Restructure the README around what users can actually do with the
plugin rather than listing technical components. Opens with the core
value prop — your AI assistant knows code, this teaches it Sentry — then
shows real examples for each use case before diving into skill tables.
Drops the plugin structure tree (internal detail) and streamlines
installation instructions. Adds a contributing section pointing to the
agent skills spec and the sdk-skill-creator skill.
Co-Authored-By: Claude (Anthropic)
Update documentation to reflect the full skill catalog ported from
sentry-agent-skills. Skills are now organized into four categories:
- SDK bundles (9): full platform setup wizards with reference docs
- Setup skills (2): AI monitoring, OTel exporter
- Workflow skills (4): code review, PR review, fix issues, create alerts
- Authoring skills (1): SDK skill creator
Also adds scripts/generate-skill-list.sh from sentry-agent-skills for
generating skill lists from SKILL.md frontmatter.
Co-Authored-By: Claude (Anthropic)
Merges `sentry-for-claude` and `sentry-for-cursor` into a single repo that serves both platforms. Both repos contained the same Sentry plugin (MCP server, skills, commands) packaged for different platforms — maintaining two repos meant duplicating every change.
Skills and commands now live at the repo root where both Claude Code and Cursor auto-discover them. Each platform gets its own metadata directory (`.claude-plugin/`, `.cursor-plugin/`) with separate `plugin.json` and `marketplace.json` files — no symlinks between platform-specific configs. MCP configs are also separate files (`.mcp.json` for Claude Code, `mcp.json` for Cursor) since the platforms use different file conventions.
`.agents/` is preserved as symlinks to `commands/` and `skills/` for backwards compatibility.
Plugin manifests validated against the official schemas from [cursor/plugins](https://github.com/cursor/plugins/tree/main/schemas) and [anthropics/claude-code](https://github.com/anthropics/claude-code).
After merge, rename repo from `sentry-for-claude` to `sentry-for-ai` and archive `sentry-for-cursor` with a redirect notice.
---------
Co-authored-by: Claude <noreply@anthropic.com>
These capabilities are being rebuilt as part of the getsentry/sentry-mcp
server. Also removes the now-redundant MCP-SETUP.md since MCP is
auto-configured via .mcp.json and plugin.json.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add sentry-ios-swift-setup skill for configuring Sentry in iOS/Swift
apps including error monitoring, tracing, session replay, logging,
and profiling. Update README and AGENTS.md with complete skills listing.
Co-Authored-By: Claude (claude-opus-4-6)
Simplify the installation process by using the official Claude marketplace
instead of requiring users to manually add a custom marketplace first.
The new single-step `/install sentry` command makes it easier for users
to get started.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add official Sentry integration plugin for Claude Code with:
- /seer command for natural language queries about Sentry environment
- /getIssues command for fetching recent issues by project
- issue-summarizer agent for parallel issue analysis
- sentry-pr-resolver skill for automated PR comment resolution
- Automatic MCP server configuration for Sentry API access
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Evan Purkhiser