sentry-verification
SkillCloud & infraVerify Sentry error capture is working after a DSN change or deploy. Use when testing Sentry, confirming error reporting works, or debugging why errors aren't showing up in the Sentry dashboard.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the sentry-verification skill
What this skill tells your AI
The instructions your AI receives, as published by vscarpenter/gsd-task-manager in .claude/skills/sentry-verification/SKILL.md and read by ahel’s review.
Sentry verification (recurring debugging task)
Development never sends events. initSentry() in lib/sentry.ts returns
early when ENV_CONFIG.isDevelopment (localhost/127.0.0.1/*.local), so a dev
server will not report to Sentry no matter what you trigger. There is no staging
deploy, so verify capture locally with the gate lifted: temporarily remove
|| ENV_CONFIG.isDevelopment from the initSentry guard, verify, then restore
it before commit.
Then:
- Confirm DSN is loaded:
console.loginlib/sentry.tswhereSentry.initruns and grep the console for it. - Trigger a test error:
captureException(new Error("manual-test-from-claude"))in a dev-only handler, OR throw from a component error boundary. - Verify in the Sentry dashboard within ~30s. Expect the message to read
"Error details redacted" — that's the privacy sanitizer working, not a
failure. Check the event's type, stack frames, and
gsdcontext instead. - Remove the test trigger (and restore the dev gate if lifted) before commit.
Signals
- GitHub stars
- 25
- Forks
- 3
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
sentry-verification- Source
- github.com/vscarpenter/gsd-task-manager