sentry-fix-verification
Verify a production fix by linking the changed code and release to Sentry issue state and post-release event trends without resolving issues prematurely.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/sentry-fix-verification && cp -r /tmp/sentry-fix-verification/examples/plugin-packages/sentry/skills/sentry-fix-verification ~/.claude/skills/sentry-fix-verificationSKILL.md
# Sentry Fix Verification 1. Record the target issue, expected fix, code change, release, environment, and observation window. 2. Confirm the release containing the change is actually present in Sentry. 3. Compare post-release events and affected users with the pre-release baseline. 4. Report whether evidence shows fixed, improving, unchanged, regressed, or insufficient traffic. 5. Change issue state only when the user requests it and the verification evidence is adequate. Keep local tests, merged code, deployed release, and observed production behavior as separate milestones.
Search and summarize material from the Acme research service.
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.