hatch3r-observability-verify

Official

Prove services are observable, not just shipped.

Authorhatch3r
Version1.0.0
Installs0

System Documentation

What problem does it solve?

It prevents teams from declaring a feature “done” when tracing, logging, metrics, SLOs, and alerting are missing or incomplete, leaving production blind during incidents.

Core Features & Use Cases

  • OTel tracing coverage gate: verifies root spans for every request path and child spans for outbound calls, plus required HTTP/DB semantic attributes.
  • Trace-correlated structured logging gate: enforces JSON logs and ensures every request-scoped log line includes trace identifiers for click-through debugging.
  • Metrics, SLOs, and alerting gates: checks RED/USE instrumentation, committed SLO + burn-rate alert review, error-tracker integration, and alerts-as-code runbooks.
  • Use case: you merged a new API route and want to ensure it has end-to-end observability (spans + trace_id logs + metrics + SLO + runbook-backed alerts) before the next release.

Quick Start

Ask a coding agent to run the observability verification gate before marking the service feature complete.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: hatch3r-observability-verify
Download link: https://github.com/hatch3r/hatch3r/archive/main.zip#hatch3r-observability-verify

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.