mirror of
https://github.com/getsentry/sentry-for-ai.git
synced 2026-09-14 14:28:22 +08:00
Evan Purkhiser
81e88c7c5c
feat(skills): add /sentry-get-started and restructure into five routers Reorganize the skill tree around a single guided entry point. Previously the three routers (sdk-setup / workflow / feature-setup) assumed the user already knew their intent, there was no orientation layer, and SDK setup never confirmed an event actually reached Sentry. Add a `/sentry-get-started` command that orients the user from a cheap probe (MCP auth, repo already using Sentry, has a project) and routes into the right skill -- sending brand-new users straight into first-error setup and showing an existing user the relevant menu. Move to five visible routers so every menu item maps 1:1 to a router the user can invoke directly later (get-started is just a first-run concierge, never the sole path to anything): sdk-setup, add-signal, improve-setup, workflow, monitors. Retire feature-setup and redistribute its skills. Separate WHAT/WHY from HOW: new platform-agnostic concept skills (tracing, logging, metrics, crons, profiling, session-replay, user-feedback) cover strategy and best practices, while the SDK skill remains the source of truth for platform mechanics and is entered scoped to a capability. Add sentry-verify-instrumentation, a shared hidden utility that closes the loop -- trigger a real event and confirm it landed via the MCP -- so no SDK skill reimplements verification. Several new improve-setup (source-maps, releases, data-scrubbing, reduce-volume, enable-ai-review) and monitors (uptime, metric-alerts, dashboards) leaves are intentionally stubs to flesh out in follow-up passes. Extend build-skill-tree.sh for the new categories/sections, regenerate SKILL_TREE.md, and update AGENTS.md. All four plugin builds validate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>