sentry

Plugin sentry from marketplace plugin-sentry in yigitkonur/plugin-sentry. Commands read from the repo's manifest — 18 days ago.

Skills (11)

• apply

  Implement the approved Sentry findings (one commit per group, fix-safety protocol), then verify them with a live event and clean up.

• audit

  Audit the Sentry setup in this repo (and optionally the Sentry org): find what is missing, wrong or risky across errors, tracing, profiling, replay, logs, crons, releases, source maps, privacy and more, then offer to fix it.

• clean

  Remove the plugin's artifacts from this repo (.sentry-plugin/, leftover temporary trigger files, the .gitignore line it added). Shows what would go first.

• doctor

  Check that this machine is ready for Sentry work: which CLI is installed, login and scopes, org region, git state, and whether Sentry's own plugins are present.

• ground-rules

  Use before writing or reviewing Sentry configuration or SDK setup: sentry.init, Sentry.init, sentry_sdk.init, sentry.client/server/edge config, instrumentation.ts, .sentryclirc, sentry.properties, SENTRY_DSN or SENTRY_AUTH_TOKEN, sentry or sentry-cli CI steps. How to work with Sentry here: look opti

• init

  Set up Sentry properly in a repo that has none: picks the install route, proposes the base setup plus extras that fit, applies only what you approve, and proves it with a live event.

• org

  Audit the Sentry organization behind this repo (projects, keys, filters, scrubbing, spike protection, alerts, monitors, releases, source maps, ownership, usage, Seer settings) with read-only probes, then apply only the org changes you approve.

• policy

  Answer the privacy, org-access, environment, volume and product questions that drive every audit and setup. Always asks, even if you answered before.

• start

  Set up, check or fix Sentry in this repo. Detects the stack, decides between auditing an existing setup and initializing a missing one, and walks it through to a verified result.

• triage

  Use when the user asks why something is failing or erroring in production, asks for the top or recent Sentry errors or regressions, mentions a Sentry alert, or names a Sentry issue (short id like API-7 or a sentry.io issues URL). Walks the CLI funnel rank, view, corroborate; Seer only on request. No

• verify

  Prove applied Sentry changes with a live marked event: arrival, readable stack trace, privacy scan of the arrived payload. Claims only the verification rung actually reached.

Subagents (3)

• auditor

  Read-only Sentry auditor for one unit and one product group of a repo (or the Sentry org). Dispatched by the audit and init flows; it writes only through sentry-ctx finding add and coverage set. Do not use for general code review.

• implementer

  Applies approved Sentry findings for one unit and one product group, one commit per group, following the fix-safety protocol. Dispatched by the apply flow; never invoked for unapproved work.

• verifier

  Independent proof for applied Sentry findings: emits a marked event from the real app, waits for it in Sentry, checks readability and privacy, and records the highest verification rung reached with evidence. Dispatched by the verify flow.

Hooks (5)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/run.sh" session-start

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run.sh" guard-write

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run.sh" gate-bash

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run.sh" stale-api

• Stop

  "${CLAUDE_PLUGIN_ROOT}/hooks/run.sh" stop-gate

Similar plugins