← ClaudeAtlas

error-tracking-auditlisted

Audits an app's error-tracking wiring against spec/project/error-tracking/ and produces a severity-classified audit artifact plus a plan for the gaps. The default `audit` operation dispatches the read-only error-tracking-audit-scanner agent, then hard-fails on any static tool-contract violation (SDK init at process entry with global handlers, DSN from deployment config, environment and release tagging, explicit sampling, default-PII off plus a wired scrubbing hook, no log-sink misuse) and on a divergent stage vocabulary; tracker-side behaviour is verify-at-runtime. The `plan` operation dispatches implementation-plan-author so a specialist (fullstack-developer) wires the fix — there is no mechanical apply. Invoke to audit error tracking or check Sentry-protocol SDK wiring; also German. Don't use for the telemetry pillars (observability-audit), the PII/GDPR verdict (gdpr-data-protection-reviewer), or red CI runs (workflow-health-triage). Supports resume.
nolte/claude-shared · ★ 0 · AI & Automation · score 74
Install: claude install-skill nolte/claude-shared
# Error Tracking Audit Audit an application's error-tracking wiring against the portfolio contract, produce a severity-classified audit artifact, and hand the gaps to a specialist as an implementation plan. The `audit` operation reports; the `plan` operation turns the findings into specialist-mapped work packages. **There is no mechanical `apply`** — SDK bootstrap, tagging, and scrubbing wiring are real code changes, so remediation is a plan a specialist implements, not an in-place rewrite. Implements `spec/project/error-tracking/`, which defines the six-capability tool class, the tool-neutral integration contract, the three lifecycle phases with their differing mandates, and the operating duties. This skill owns policy, severity, the report, and the handover; detection belongs to the `error-tracking-audit-scanner` agent. Delimitation, mirroring the spec's own: `observability-audit` (`spec/project/monitoring-observability/`) owns the four telemetry pillars, the browser error-listener floor, the third-party floor, and the cardinality and PII-redaction guardrails; this skill owns the **error-tracking tool layer** those events land in. `gdpr-data-protection-reviewer` owns the PII-class definition and the leak verdict — here only *that* scrubbing is wired is checked. `api-error-check` owns the error *response* contract an API returns to clients. `workflow-health-triage` owns red CI runs; the tracker watches running applications, not pipelines. The spec's SDK-currency MUST (tra